Triple
T5653218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian Games torch relay |
E124554
|
entity |
| Predicate | routeMayInclude |
P65442
|
FINISHED |
| Object | multiple Asian countries |
—
|
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: multiple Asian countries | Statement: [Asian Games torch relay, routeMayInclude, multiple Asian countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeMayInclude Context triple: [Asian Games torch relay, routeMayInclude, multiple Asian countries]
-
A.
mayRouteTo
Indicates that one entity is permitted or able to direct, forward, or transfer something (such as data, traffic, or requests) to another entity.
-
B.
routeExtension
Indicates that an existing route is extended beyond its original endpoint to cover additional segments or destinations.
-
C.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
D.
routeRole
Indicates the specific functional role or purpose that an entity has within a particular route or path.
-
E.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
- F. None of above. chosen
Provenance (4 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022d8a2588190b10de59edbc8841f |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2274b48190b2ef57ed728f785c |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0727bc8190b16e9a669c04b4dd |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:42 p.m.