Triple
T25078669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taiwan provincial highway system |
E628121
|
entity |
| Predicate | hasRoutePrefix |
P66954
|
FINISHED |
| Object | Taiwan Provincial Highway |
—
|
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: Taiwan Provincial Highway | Statement: [Taiwan provincial highway system, hasRoutePrefix, Taiwan Provincial Highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoutePrefix Context triple: [Taiwan provincial highway system, hasRoutePrefix, Taiwan Provincial Highway]
-
A.
hasPrefix
chosen
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
B.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
C.
hasSuffixedRoute
Indicates that a route is a variant or extension of another base route, distinguished by an added suffix in its identifier.
-
D.
hasRouteStart
Indicates that one entity serves as the starting point or origin location for a specified route associated with another entity.
-
E.
hasRouteName
Indicates that a route, path, or connection is associated with a specific name or label.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 6:21 a.m.