Triple
T33924555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bristol Type 200 |
E869711
|
entity |
| Predicate | neverBuilt |
P177912
|
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: [Bristol Type 200, neverBuilt, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neverBuilt Context triple: [Bristol Type 200, neverBuilt, true]
-
A.
neverCompletedAs
Indicates that an entity was at some point expected or intended to have a certain role, status, or outcome, but that role/status/outcome was never actually completed or realized.
-
B.
builtWithout
Indicates that something was constructed or created in the absence of a particular component, material, tool, or condition.
-
C.
neverLaunched
Indicates that an entity (such as a product, project, or mission) was planned or created but was never officially initiated, released, or put into operation.
-
D.
notRebuiltAfter
Indicates that an entity was destroyed or damaged and has not been reconstructed or restored after a specified event or point in time.
-
E.
never
Indicates that the specified relationship or action does not occur at any time or under any circumstances.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f7064d37388190993b2a7305a02b9f |
completed | May 3, 2026, 8:24 a.m. |
Created at: May 1, 2026, 1:49 a.m.