Triple
T22471055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savoia-Marchetti S.56 |
E555500
|
entity |
| Predicate | typicalCrewRole |
P18942
|
FINISHED |
| Object | pilot |
—
|
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: pilot | Statement: [Savoia-Marchetti S.56, typicalCrewRole, pilot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCrewRole Context triple: [Savoia-Marchetti S.56, typicalCrewRole, pilot]
-
A.
crewType
Indicates the specific role or category of crew associated with an entity, such as the type of personnel assigned to operate or support it.
-
B.
typicalRole
chosen
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
C.
typicalAdditionalRole
Indicates that an entity commonly or characteristically holds an extra role or function in addition to its primary one.
-
D.
coCrewMember
Indicates that two or more individuals serve together as members of the same crew on a shared mission, vehicle, or operation.
-
E.
crew
Indicates that one entity serves as the group of people who operate, staff, or work on another entity (such as a vehicle, vessel, or production).
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15bdf6dfc8190aa8dc80ad92a9267 |
completed | April 29, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.