Triple
T34347085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nimrod AEW3 |
E881463
|
entity |
| Predicate | crewComplementIntended |
P145900
|
FINISHED |
| Object | flight crew and mission specialists |
—
|
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: flight crew and mission specialists | Statement: [Nimrod AEW3, crewComplementIntended, flight crew and mission specialists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewComplementIntended Context triple: [Nimrod AEW3, crewComplementIntended, flight crew and mission specialists]
-
A.
intendedCrew
chosen
Indicates that an entity is designated or planned to serve as the crew for another entity (such as a vehicle, mission, or operation).
-
B.
crewOnboard
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
C.
crewComplementType
Indicates the classification or category of a crew complement associated with an entity (such as its role, composition, or staffing type).
-
D.
crewComplementStatusOnLaunch
Indicates the status or condition of a vehicle’s assigned crew complement at the moment of launch.
-
E.
crewOnReturn
Indicates that a crew member is assigned to be on board a specific vehicle, mission, or vessel for its return journey.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:58 a.m.