Triple
T28851796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tehran Metro Line 6 at Shohada-ye Haftom-e Tir |
E728617
|
entity |
| Predicate | keyTransferPoint |
P153529
|
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 6 at Shohada-ye Haftom-e Tir, keyTransferPoint, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyTransferPoint Context triple: [Tehran Metro Line 6 at Shohada-ye Haftom-e Tir, keyTransferPoint, true]
-
A.
keyTransitArea
chosen
Indicates that a location functions as a primary passage or hub through which movement or transport between other areas is concentrated or facilitated.
-
B.
keyCenter
Indicates the central or primary tonal focus around which other related elements are organized or interpreted.
-
C.
keyPosition
Indicates the specific location or placement of a key within a defined space or system.
-
D.
keyTarget
Indicates that one entity serves as the primary focus, objective, or intended recipient of another entity’s action, function, or influence.
-
E.
keyHub
Indicates a central or primary element that connects, coordinates, or controls multiple related components or interactions.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f659d910788190b8cbcd7eaea9f16a |
completed | May 2, 2026, 8:08 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:44 a.m.