Triple
T2163724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curitiba BRT system |
E46858
|
entity |
| Predicate | boardingMethod |
P8856
|
FINISHED |
| Object | all-door boarding |
—
|
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: all-door boarding | Statement: [Curitiba BRT system, boardingMethod, all-door boarding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardingMethod Context triple: [Curitiba BRT system, boardingMethod, all-door boarding]
-
A.
boardingProcess
chosen
Indicates the process or sequence of actions by which passengers move from a waiting area onto a vehicle (such as an airplane, train, or bus).
-
B.
boarding
Indicates that one entity is getting onto or entering a vehicle, vessel, or similar conveyance associated with another entity.
-
C.
submissionMethod
Indicates the means or channel through which something is submitted or delivered.
-
D.
appointmentMethod
Indicates how an appointment is arranged, such as the channel, process, or means used to schedule it.
-
E.
mobilizationMethod
Indicates the method or process by which resources, people, or assets are organized and activated for a particular purpose or operation.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe8d105c819098371c35c88873dc |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.