Triple
T34463709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coalbrookdale |
E884711
|
entity |
| Predicate | hasStructureTypeProduced |
P64053
|
FINISHED |
| Object | cast-iron bridges |
—
|
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: cast-iron bridges | Statement: [Coalbrookdale, hasStructureTypeProduced, cast-iron bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStructureTypeProduced Context triple: [Coalbrookdale, hasStructureTypeProduced, cast-iron bridges]
-
A.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
B.
producesStructure
chosen
Indicates that one entity generates, forms, or creates a physical or conceptual structure as a result of its action or function.
-
C.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
D.
hasStructureModel
Indicates that an entity is associated with, or represented by, a specific structural model.
-
E.
hasStructureCode
Indicates that an entity is associated with a specific structural identifier or code that defines its organization or configuration.
- 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff97637ad881908c24fe2cc6b036db |
completed | May 9, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69ff96c43a808190942eeda1934602db |
completed | May 9, 2026, 8:19 p.m. |
Created at: May 1, 2026, 2 a.m.