Triple
T4538867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General der Jagdflieger |
E107476
|
entity |
| Predicate | oversawPersonnelType |
P41763
|
FINISHED |
| Object | fighter 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: fighter pilots | Statement: [General der Jagdflieger, oversawPersonnelType, fighter pilots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oversawPersonnelType Context triple: [General der Jagdflieger, oversawPersonnelType, fighter pilots]
-
A.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
B.
oversawUnitType
chosen
Indicates that an entity had supervisory or managerial responsibility over a particular type or category of unit.
-
C.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
D.
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.
-
E.
authorizedPersonnel
Indicates that the referenced entity is officially permitted or empowered to access, use, or perform actions within a specified system, resource, or context.
- 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_69bd43f922788190b7edfa294e39b178 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57ba327c8190a7f12e14077b1fa7 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:04 p.m.