Triple
T8067357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Völklingen Ironworks |
E188276
|
entity |
| Predicate | constructedTo |
P80317
|
FINISHED |
| Object | 1883 |
—
|
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: 1883 | Statement: [Völklingen Ironworks, constructedTo, 1883]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructedTo Context triple: [Völklingen Ironworks, constructedTo, 1883]
-
A.
constructedAs
Indicates that one entity is built, formed, or created in the manner, structure, or configuration specified by another entity.
-
B.
constructedUnder
Indicates that something was built, created, or assembled while subject to the authority, direction, or conditions imposed by a particular agent, rule, plan, or regime.
-
C.
constructedDuring
Indicates that one entity was built or created within the time period defined by another entity or event.
-
D.
createdByConstructionOf
Indicates that something comes into existence as a result of a construction process or building activity performed by an agent.
-
E.
ledToConstructionOf
Indicates that one entity caused, initiated, or was the primary reason for the construction or creation of another entity.
- 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ff75d208190b7c53d2fe55878ac |
completed | March 31, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:26 p.m.