Triple
T1162677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daimler-Benz DB 601 |
E24527
|
entity |
| Predicate | applicationRole |
P12085
|
FINISHED |
| Object | fighter aircraft |
—
|
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: fighter aircraft | Statement: [Daimler-Benz DB 601, applicationRole, fighter aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationRole Context triple: [Daimler-Benz DB 601, applicationRole, fighter aircraft]
-
A.
securityRole
Indicates that an entity holds a specific security-related role, permission level, or access profile within a system or context.
-
B.
systemRole
chosen
Indicates the functional position or responsibility that an entity holds within a larger system or structure.
-
C.
definesRole
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
-
D.
testRole
Indicates that an entity is assigned or associated with a specific role used for testing or validation purposes.
-
E.
identificationRole
Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing another entity.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcb2bb84819088bd94e91c10fb0c |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.