Triple
T9944045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PB4Y-2 Privateer |
E194155
|
entity |
| Predicate | tailModification |
P3547
|
FINISHED |
| Object | single tall vertical fin replacing B-24 twin tail |
—
|
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: single tall vertical fin replacing B-24 twin tail | Statement: [PB4Y-2 Privateer, tailModification, single tall vertical fin replacing B-24 twin tail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tailModification Context triple: [PB4Y-2 Privateer, tailModification, single tall vertical fin replacing B-24 twin tail]
-
A.
tailConfiguration
chosen
Indicates how the tail of an entity is arranged, structured, or positioned relative to the rest of that entity.
-
B.
leafModification
Indicates a relationship where an entity undergoes or causes a change in the structure, form, or characteristics of a leaf.
-
C.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
D.
tailCharacteristic
Indicates that an entity possesses a particular property, feature, or quality specifically related to its tail.
-
E.
modification
Indicates a change made to an existing entity, altering its properties, structure, or state from a prior version.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb613fbb48190b82a06987310cc96 |
completed | April 2, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.