Triple
T16954258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jagdgeschwader 7 |
E411255
|
entity |
| Predicate | usedJetAircraft |
P125376
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Jagdgeschwader 7, usedJetAircraft, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedJetAircraft Context triple: [Jagdgeschwader 7, usedJetAircraft, true]
-
A.
referredAircraftUsedFor
Indicates that the referenced aircraft is utilized for a particular purpose, role, or operation in relation to another entity or context.
-
B.
referredAircraftUsedIn
Indicates that an aircraft being referred to is the one that was actually used in a particular event, operation, or context.
-
C.
previousAircraftUsed
Indicates that one aircraft was used immediately before another in a sequence of aircraft usage.
-
D.
usedByAircraftRegisteredIn
Indicates that something (such as equipment, a system, or a facility) is utilized by aircraft that are registered in a specified jurisdiction or registry.
-
E.
usedAircraftOrigin
Indicates the place or source from which a used aircraft was originally obtained or came.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01b04e88190a72735541b3bb117 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:31 a.m.