Triple
T11067633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympiades |
E261665
|
entity |
| Predicate | lineTechnology |
P14437
|
FINISHED |
| Object | rubber-tyred metro |
—
|
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: rubber-tyred metro | Statement: [Olympiades, lineTechnology, rubber-tyred metro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineTechnology Context triple: [Olympiades, lineTechnology, rubber-tyred metro]
-
A.
technologyLineage
Indicates a relationship where one technology is derived from, influenced by, or evolved from another in a historical or developmental sequence.
-
B.
lineUse
Indicates how a particular line (such as a route, track, or service line) is utilized or purposed within a system or network.
-
C.
lineTerminal2
Indicates that the referenced entity serves as the second terminal (endpoint) of a line.
-
D.
lineUses
chosen
Indicates that a particular line (such as a route, service, or connection) makes use of or is implemented using a specified resource, infrastructure, or element.
-
E.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
- 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_69d79920428c81908db824ab54e08e8d |
completed | April 9, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.