Triple
T28932944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinkel He 162 |
E733835
|
entity |
| Predicate | programPriority |
P170674
|
FINISHED |
| Object | emergency fighter program |
—
|
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: emergency fighter program | Statement: [Heinkel He 162, programPriority, emergency fighter program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programPriority Context triple: [Heinkel He 162, programPriority, emergency fighter program]
-
A.
planningPriority
Indicates the relative importance or urgency assigned to an item, task, or objective when organizing or scheduling plans.
-
B.
managementPriority
Indicates the relative level of importance or urgency assigned to managing or addressing a particular entity, issue, or task.
-
C.
priorityApplication
Indicates that one application is given precedence or higher processing priority over others.
-
D.
priorityGroup
Indicates that one entity is assigned to, or associated with, a particular level or category of priority relative to others.
-
E.
priorityDeterminedBy
Indicates that the priority or importance level of one entity is established based on another entity or set of factors.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 28, 2026, 8:29 a.m.