Triple
T6787397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specification P.13/36 |
E155844
|
entity |
| Predicate | aircraftRoleRequired |
P72991
|
FINISHED |
| Object | heavy bomber |
—
|
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: heavy bomber | Statement: [Specification P.13/36, aircraftRoleRequired, heavy bomber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftRoleRequired Context triple: [Specification P.13/36, aircraftRoleRequired, heavy bomber]
-
A.
aircraftRoleSupported
Indicates that a given role or function is supported or enabled for a particular aircraft.
-
B.
testAircraftRole
Indicates that an aircraft is assigned or evaluated for a specific operational role or function.
-
C.
usedOnAircraftRole
Indicates that something is employed or applied in the context of a specific role or function on an aircraft.
-
D.
referredAircraftRole
Indicates that one aircraft is mentioned or designated in relation to another aircraft’s role, function, or status within a specific context or event.
-
E.
basedAircraftRole
Indicates that an aircraft is regularly stationed at a particular location in a specified operational role or function.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2907d0081908291aad66048b8b1 |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1b0d2a48190b249dcc671b9b5e4 |
completed | March 27, 2026, 6:51 p.m. |
Created at: March 27, 2026, 2:14 p.m.