Triple
T30225731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 89 |
E768472
|
entity |
| Predicate | terminusCityArea |
P176333
|
FINISHED |
| Object | Caribou metropolitan area |
—
|
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: Caribou metropolitan area | Statement: [Maine State Route 89, terminusCityArea, Caribou metropolitan area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusCityArea Context triple: [Maine State Route 89, terminusCityArea, Caribou metropolitan area]
-
A.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
B.
cityCenterTerminusArea
Indicates that the referenced area serves as the terminus or end-point of a route or line located in or at the center of a city.
-
C.
terminusCitySouth
Indicates that something serves as the southern terminus or endpoint located in a particular city.
-
D.
terminusAreaUse
Indicates how the area of a terminus (such as a station or endpoint facility) is utilized or functionally designated.
-
E.
terminusBorough
Indicates the borough in which the endpoint or terminus of something (such as a route or line) is located.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 29, 2026, 7:35 p.m.