Triple
T16618576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bailey bridge |
E403759
|
entity |
| Predicate | isPrefabricated |
P70588
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bailey bridge, isPrefabricated, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrefabricated Context triple: [Bailey bridge, isPrefabricated, true]
-
A.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
B.
isFabricated
chosen
Indicates that something has been artificially made, constructed, or invented rather than naturally occurring or genuinely existing.
-
C.
builtAsPartOf
Indicates that one entity was constructed as a component or subset of a larger, encompassing entity or project.
-
D.
isEngineeredStructure
Indicates that something is a man-made or artificially constructed structure, typically designed and built through engineering processes.
-
E.
isBuiltFor
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3754bc4cc8190a586732fc6507b40 |
completed | April 18, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.