Triple
T25681568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armstrong Whitworth Albemarle |
E643952
|
entity |
| Predicate | laterRoleChange |
P138651
|
FINISHED |
| Object | transport and glider tug |
—
|
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: transport and glider tug | Statement: [Armstrong Whitworth Albemarle, laterRoleChange, transport and glider tug]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRoleChange Context triple: [Armstrong Whitworth Albemarle, laterRoleChange, transport and glider tug]
-
A.
subsequentRole
chosen
Indicates that one role or position is held after, and in succession to, another role or position.
-
B.
laterVariantRole
Indicates that one role is a subsequent or later variant of another, reflecting a modified or evolved version of the original role.
-
C.
laterPrimaryRole
Indicates that an entity assumes a specified primary role at a later time than another role or state in a sequence.
-
D.
laterEnforcementRole
Indicates that an entity assumes or is assigned an enforcement-related role at a later time relative to another role, event, or time period.
-
E.
roleChangeLaterWar
Indicates that an entity’s role or position changes at a later stage within the context of a war or armed conflict.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 21, 2026, 8:01 p.m.