Triple
T8097050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tehran Metro Line 8 |
E189010
|
entity |
| Predicate | isInPlanningOrOperation |
P24929
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tehran Metro Line 8, isInPlanningOrOperation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInPlanningOrOperation Context triple: [Tehran Metro Line 8, isInPlanningOrOperation, true]
-
A.
isOperatedIn
Indicates that an entity carries out its operations or activities within a specified location, region, or jurisdiction.
-
B.
hasPlanningStatus
chosen
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
-
C.
hasPlanningLevel
Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
-
D.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
E.
usedInOperation
Indicates that something (such as a tool, method, or resource) is employed or applied during the execution of a particular operation or procedure.
- 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_69ca82b886d88190a9cba0d5a4a27521 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb429319048190b612c8060a9a24d2 |
completed | March 31, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:30 p.m.