Triple
T28103395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County Road 550 |
E710295
|
entity |
| Predicate | terminusCommunityType |
P3292
|
FINISHED |
| Object | unincorporated community |
—
|
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: unincorporated community | Statement: [County Road 550, terminusCommunityType, unincorporated community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusCommunityType Context triple: [County Road 550, terminusCommunityType, unincorporated community]
-
A.
terminusType
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
-
B.
hasCommunityAtTerminus
Indicates that a transportation route or line has a community located at or directly associated with its endpoint or terminus.
-
C.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
-
D.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
E.
hasCommunityType
chosen
Indicates that an entity is associated with or classified under a particular type or category of community.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 9:06 p.m.