Triple
T5168673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-Iranian Railway |
E116620
|
entity |
| Predicate | builtWithout |
P61918
|
FINISHED |
| Object | foreign loans |
—
|
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: foreign loans | Statement: [Trans-Iranian Railway, builtWithout, foreign loans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtWithout Context triple: [Trans-Iranian Railway, builtWithout, foreign loans]
-
A.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
B.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
-
C.
builtWithAssistanceFrom
Indicates that something was constructed, created, or developed with help, support, or collaboration from another party.
-
D.
builtAsPartOf
Indicates that one entity was constructed as a component or subset of a larger, encompassing entity or project.
-
E.
builtToMark
Indicates that something was constructed for the purpose of commemorating, signaling, or designating a particular event, place, boundary, or significance.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd794dd9988190922e138f2a9a3c62 |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78d6a1388190804dcf568ca92129 |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:45 p.m.