Triple
T10246660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Raza |
E240231
|
entity |
| Predicate | hasHighPassengerTraffic |
P35231
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [La Raza, hasHighPassengerTraffic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighPassengerTraffic Context triple: [La Raza, hasHighPassengerTraffic, true]
-
A.
hasHeavyPassengerTraffic
chosen
Indicates that an entity experiences a high volume of passenger movement or usage over a given period.
-
B.
hasHeavyTraffic
Indicates that a location, route, or area is experiencing a high volume of traffic, causing congestion or delays.
-
C.
hasPassengerTrafficFrom
Indicates that an entity receives or handles passenger traffic originating from another entity.
-
D.
handlesMostPassengerTrafficOf
Indicates that one entity is responsible for managing the largest share of passenger traffic associated with another entity, compared to all similar entities.
-
E.
hasPassengerTrafficRank
Indicates the relative position or ranking of an entity based on the volume of passenger traffic it handles compared to others.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:27 a.m.