Triple
T2104524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eighth Air Force |
E37161
|
entity |
| Predicate | notableTargetType |
P35851
|
FINISHED |
| Object | German aircraft industry |
—
|
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: German aircraft industry | Statement: [Eighth Air Force, notableTargetType, German aircraft industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTargetType Context triple: [Eighth Air Force, notableTargetType, German aircraft industry]
-
A.
notableTarget
Indicates that the subject is particularly significant, prominent, or noteworthy with respect to the specified target.
-
B.
notableProjectType
Indicates the type or category of a project for which an entity is particularly well-known or notable.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notableBase
Indicates that a particular location serves as a significant or distinguished base or headquarters for an entity.
-
E.
notableServiceType
Indicates that the subject is associated with a particular type or category of service that is especially notable or significant.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabf7cdc81909636dff34badc1c5 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb9ce3ff08190a9501f8bb821c01c |
completed | March 7, 2026, 5:38 a.m. |
Created at: March 4, 2026, 7:43 p.m.