Triple
T7071709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumbuco |
E164713
|
entity |
| Predicate | hasTransportOption |
P1298
|
FINISHED |
| Object | road access from Fortaleza |
—
|
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: road access from Fortaleza | Statement: [Cumbuco, hasTransportOption, road access from Fortaleza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportOption Context triple: [Cumbuco, hasTransportOption, road access from Fortaleza]
-
A.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
B.
hasGroundTransportation
chosen
Indicates that an entity provides, includes, or is connected to transportation services or options that operate on land (e.g., cars, buses, trains).
-
C.
hasBoardingOption
Indicates that an entity offers or is associated with a particular way or method by which passengers or items can board or be taken on.
-
D.
hasTransportCategory
Indicates that one entity is classified under a particular category or type of transport associated with another entity.
-
E.
hasTransportationContext
Indicates that there is a contextual relationship involving transportation modes, conditions, or circumstances relevant to the associated entities or event.
- 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_69c6887b96548190a8a9b3ac8adf4119 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4c9cdbc8190b91cd3b4eef58eb6 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:39 p.m.