Triple
T25169742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landore Viaduct |
E630285
|
entity |
| Predicate | structureClass |
P157987
|
FINISHED |
| Object | bridge |
—
|
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: bridge | Statement: [Landore Viaduct, structureClass, bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structureClass Context triple: [Landore Viaduct, structureClass, bridge]
-
A.
structureFunction
Indicates that one entity’s physical or organizational structure serves a particular function or role in relation to another entity.
-
B.
structureConstants
Indicates that the given values are the structure constants specifying how basis elements of an algebra (or Lie algebra) multiply or bracket to produce linear combinations of other basis elements.
-
C.
securityClassStructure
Indicates a hierarchical or organizational relationship defining how security classifications are structured or arranged relative to one another.
-
D.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
-
E.
definesStructure
Indicates that one entity specifies or determines the organizational form, composition, or arrangement 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46d44f48c8190943b3b22651be3c4 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 12:19 p.m.