Triple
T7572170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Road 200 |
E179269
|
entity |
| Predicate | continuesToward |
P77537
|
FINISHED |
| Object | Gainesville area |
—
|
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: Gainesville area | Statement: [State Road 200, continuesToward, Gainesville area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuesToward Context triple: [State Road 200, continuesToward, Gainesville area]
-
A.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
B.
continuesToControl
Indicates that one entity maintains ongoing authority, influence, or command over another entity or resource over time.
-
C.
continuityFrom
Indicates that one entity continues, extends, or proceeds directly from another in a seamless or unbroken manner.
-
D.
goesOn
Indicates that one entity participates in, boards, or travels using another entity, such as a vehicle, trip, or event.
-
E.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
- F. None of above. chosen
Provenance (4 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f921b458819092e565a4d099bbaf |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f5b1a6a08190b9ff2bc8a7befe0d |
completed | March 27, 2026, 9:25 p.m. |
Created at: March 27, 2026, 3:51 p.m.