Triple
T22660909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluebird CN7 |
E559657
|
entity |
| Predicate | postRebuildModifications |
P42870
|
FINISHED |
| Object | revised tail fin |
—
|
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: revised tail fin | Statement: [Bluebird CN7, postRebuildModifications, revised tail fin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postRebuildModifications Context triple: [Bluebird CN7, postRebuildModifications, revised tail fin]
-
A.
laterModification
chosen
Indicates that one entity is a modification or revision that occurs after another in time.
-
B.
laterRebuiltAs
Indicates that one entity was reconstructed or redeveloped at a later time to become or be replaced by another specific entity.
-
C.
rebuild
Indicates restoring or constructing again something that was previously built, often after damage, destruction, or significant alteration.
-
D.
rebuiltAfterEvent
Indicates that an entity was reconstructed or restored following a specific event that caused damage, destruction, or significant alteration.
-
E.
majorRebuildCompleted
Indicates that a significant reconstruction or overhaul of an entity has been fully completed.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765edf88819086c28525e3c73758 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:07 p.m.