Triple
T37639654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commonwealth, Quezon City |
E936579
|
entity |
| Predicate | roadNameDerivedFrom |
P128235
|
FINISHED |
| Object | Commonwealth Avenue |
—
|
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: Commonwealth Avenue | Statement: [Commonwealth, Quezon City, roadNameDerivedFrom, Commonwealth Avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadNameDerivedFrom Context triple: [Commonwealth, Quezon City, roadNameDerivedFrom, Commonwealth Avenue]
-
A.
roadName
Indicates the specific name assigned to a road that identifies it within a transportation or address system.
-
B.
roadNameAlongRoute
Indicates that a specific road name is associated with, or used along, a particular segment or portion of a route.
-
C.
isNamedRoadIn
Indicates that a specific named road is located within or belongs to a particular geographic area or region.
-
D.
namedAfterStreet
Indicates that an entity’s name is derived from or taken in honor of a particular street.
-
E.
hasStreetNameOrigin
chosen
Indicates that the origin or source of a street’s name is specified or linked to a particular cause, person, event, or feature.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.