Triple
T36882502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manila–Davao |
E911516
|
entity |
| Predicate | hasRouteNotation |
P55683
|
FINISHED |
| Object | Manila–Davao |
—
|
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: Manila–Davao | Statement: [Manila–Davao, hasRouteNotation, Manila–Davao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteNotation Context triple: [Manila–Davao, hasRouteNotation, Manila–Davao]
-
A.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
B.
hasNotableRoute
Indicates that an entity (such as a transportation service or pathway) includes or is associated with a route that is considered significant, well-known, or otherwise noteworthy.
-
C.
hasRouteName
chosen
Indicates that a route, path, or connection is associated with a specific name or label.
-
D.
hasRouteIdentifier
Indicates that an entity is associated with a specific route code or identifier used to distinguish it from other routes.
-
E.
hasRouteConsideration
Indicates that one entity takes another entity into account when planning, evaluating, or determining a route.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:13 p.m.