Triple
T16504982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Heavy Helicopter Squadron |
E400902
|
entity |
| Predicate | aircrewComposition |
P88726
|
FINISHED |
| Object | pilots |
—
|
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: pilots | Statement: [Marine Heavy Helicopter Squadron, aircrewComposition, pilots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircrewComposition Context triple: [Marine Heavy Helicopter Squadron, aircrewComposition, pilots]
-
A.
airWingPersonnel
Indicates that the subject is a member of, or assigned as personnel to, an air wing unit.
-
B.
crewComplementWorldWarII
Indicates the typical number and composition of crew members assigned to operate a vessel or vehicle during World War II.
-
C.
crewComplementType
chosen
Indicates the classification or category of a crew complement associated with an entity (such as its role, composition, or staffing type).
-
D.
airForceUser
Indicates that an entity is a member of, affiliated with, or acting on behalf of an air force organization.
-
E.
aircraftInFleet
Indicates that a particular aircraft is included as a member of a specified fleet.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e51ce1c81909548298f703a7ffa |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.