Triple
T137335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MARC Train |
E2774
|
entity |
| Predicate | peakDirection |
P1101
|
FINISHED |
| Object | oriented toward Washington, D.C. |
—
|
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: oriented toward Washington, D.C. | Statement: [MARC Train, peakDirection, oriented toward Washington, D.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakDirection Context triple: [MARC Train, peakDirection, oriented toward Washington, D.C.]
-
A.
orientation
chosen
Indicates the relative directional alignment or facing of one entity with respect to another or to a reference frame.
-
B.
parentPeak
Indicates that one peak is the higher or primary peak to which another, subordinate peak is topographically related.
-
C.
beam
Indicates that one entity emits, directs, or projects a concentrated line or stream (such as light, energy, or information) toward another entity.
-
D.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
E.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a6cab88190944c8f74d8d1605c |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25652efdc8190b85b33735a9e6370 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.