Triple
T28577869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 82 in Georgia |
E723291
|
entity |
| Predicate | continuesWestInto |
P54719
|
FINISHED |
| Object | Alabama |
—
|
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: Alabama | Statement: [U.S. Route 82 in Georgia, continuesWestInto, Alabama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuesWestInto Context triple: [U.S. Route 82 in Georgia, continuesWestInto, Alabama]
-
A.
continuesInto
Indicates that one entity extends forward in time, space, or sequence so that it directly proceeds into and forms a continuous progression with another entity.
-
B.
westernContinuation
chosen
Indicates that one entity is the western extension or continuation of another entity in space or geography.
-
C.
continuesToward
Indicates that an entity maintains its movement or progression in the direction of a specified target or destination.
-
D.
easternContinuationLeadsTo
Indicates that a path, route, or extension continues eastward from a given point and leads to another location or state.
-
E.
runsWestFrom
Indicates that one entity extends or moves in a westward direction starting from 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 4:13 a.m.