Triple
T24666035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SH 6 |
E610678
|
entity |
| Predicate | runsDiagonallyAcross |
P130287
|
FINISHED |
| Object | Texas |
—
|
NE NERFINISHED |
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: Texas | Statement: [SH 6, runsDiagonallyAcross, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsDiagonallyAcross Context triple: [SH 6, runsDiagonallyAcross, Texas]
-
A.
runsDiagonally
chosen
Indicates that one entity extends or moves in a diagonal direction relative to another reference frame or axis.
-
B.
runsAcross
Indicates that one entity moves quickly on foot from one side of another entity, area, or boundary to the opposite side, traversing it in a roughly straight path.
-
C.
runsDirection
Indicates that an entity moves or operates in a specified direction.
-
D.
runsDirectlyOver
Indicates that one entity passes or extends immediately above another along its length or span, without significant vertical separation or intervening structures.
-
E.
diagonalRepresents
Indicates that a diagonal in a figure or matrix stands for, encodes, or symbolizes a particular value, property, or relationship.
- 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:40 a.m.