Triple
T11071851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyway |
E261763
|
entity |
| Predicate | urbanRoadNetworkRole |
P25845
|
FINISHED |
| Object | major north–south corridor in Metro Manila |
—
|
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: major north–south corridor in Metro Manila | Statement: [Skyway, urbanRoadNetworkRole, major north–south corridor in Metro Manila]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanRoadNetworkRole Context triple: [Skyway, urbanRoadNetworkRole, major north–south corridor in Metro Manila]
-
A.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
B.
hasMajorTransportationRole
Indicates that an entity plays a primary or significant role in providing or supporting transportation services or infrastructure.
-
C.
roadNetworkPartOf
Indicates that one road network segment or component is a constituent part of a larger road network.
-
D.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
E.
roadSystemRole
chosen
Indicates the specific functional role or responsibility an entity has within a road or transportation network system.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7994bbb30819090410bd3d0fde33c |
completed | April 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.