Triple
T5064409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messerschmitt |
E114107
|
entity |
| Predicate | Me410Role |
P40371
|
FINISHED |
| Object | heavy fighter and fast bomber |
—
|
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: heavy fighter and fast bomber | Statement: [Messerschmitt, Me410Role, heavy fighter and fast bomber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Me410Role Context triple: [Messerschmitt, Me410Role, heavy fighter and fast bomber]
-
A.
unitRole
chosen
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
B.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
C.
definesRole
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
-
D.
roleAtMidway
Indicates that an entity holds or held a specific role, position, or function at the midpoint or intermediate stage of a process, event, or time period.
-
E.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd747756bc8190863c426e6fd6e8f7 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.