Triple
T15422174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immelmann turn |
E369407
|
entity |
| Predicate | typicalEntryPhase |
P118726
|
FINISHED |
| Object | level flight |
—
|
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: level flight | Statement: [Immelmann turn, typicalEntryPhase, level flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEntryPhase Context triple: [Immelmann turn, typicalEntryPhase, level flight]
-
A.
typicalEntryType
Indicates the usual or standard category or kind of entry associated with something.
-
B.
typicalUsagePhase
Indicates the phase or stage in which something is most commonly or characteristically used.
-
C.
typicalEntryFile
Indicates that a given file is the standard or primary entry point typically used to start or access something (such as a program, project, or package).
-
D.
typicalEntryRoute
Indicates the usual or most common path or method by which something is entered or accessed.
-
E.
typicalEventPhase
Indicates the usual or characteristic phase within the progression of an event or process.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ebe7b1081908e6b9e6e128a8d5d |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:20 a.m.