Triple
T32194654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Octagon Earthworks |
E822370
|
entity |
| Predicate | orientationToward |
P1101
|
FINISHED |
| Object | moonrise positions |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: moonrise positions | Statement: [Octagon Earthworks, orientationToward, moonrise positions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orientationToward Context triple: [Octagon Earthworks, orientationToward, moonrise positions]
-
A.
orientationType
Indicates the specific kind or category of orientation relationship that exists between entities (such as spatial, directional, or alignment-based orientation).
-
B.
orientation
chosen
Indicates the relative directional alignment or facing of one entity with respect to another or to a reference frame.
-
C.
orientationInducedBy
Indicates that the orientation of one entity is determined or caused by the orientation or configuration of another entity.
-
D.
orientedFrom
Indicates that one entity has a defined direction or orientation starting at or determined by another reference entity.
-
E.
locationOrientation
Indicates how one entity is spatially oriented or positioned relative to a specific location or reference point.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb35e9a08190bb96bb25c32e0812 |
completed | May 3, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:35 a.m.