Triple
T28587296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copper Horse |
E723542
|
entity |
| Predicate | hasViewAlong |
P854
|
FINISHED |
| Object | axis of the Long Walk |
—
|
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: axis of the Long Walk | Statement: [Copper Horse, hasViewAlong, axis of the Long Walk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewAlong Context triple: [Copper Horse, hasViewAlong, axis of the Long Walk]
-
A.
hasViewingPointFor
Indicates that one entity serves as a vantage point or location from which another entity can be viewed or observed.
-
B.
hasViewThrough
Indicates that one entity can be seen or visually perceived through another entity acting as an intermediate medium or opening.
-
C.
hasView
chosen
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
-
D.
hasFieldOfView
Indicates that one entity possesses a visual coverage area within which it can perceive or detect other entities or regions.
-
E.
hasInclinationToLineOfSight
Indicates that one entity is oriented or directed in such a way that it tends toward having a line of sight to another entity or location.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 4:18 a.m.