Triple
T13466341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nkana, Northern Rhodesia |
E311509
|
entity |
| Predicate | infrastructureBuiltFor |
P8196
|
FINISHED |
| Object | supporting copper mining operations |
—
|
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: supporting copper mining operations | Statement: [Nkana, Northern Rhodesia, infrastructureBuiltFor, supporting copper mining operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infrastructureBuiltFor Context triple: [Nkana, Northern Rhodesia, infrastructureBuiltFor, supporting copper mining operations]
-
A.
roadBuiltFor
Indicates that a road was constructed specifically to serve, provide access to, or support the use or needs of a particular entity.
-
B.
isBuiltFor
chosen
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
-
C.
railwayBuiltFor
Indicates that a railway was constructed to serve, support, or provide access to a particular entity or purpose.
-
D.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
E.
builtInThe
Indicates that something was constructed or created within a specified location, structure, or context.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf101a1081909f2aba6da47baacc |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.