Triple
T31744375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V-bomber force |
E810228
|
entity |
| Predicate | VulcanRole |
P172497
|
FINISHED |
| Object | delta-wing high-altitude 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: delta-wing high-altitude bomber | Statement: [V-bomber force, VulcanRole, delta-wing high-altitude bomber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VulcanRole Context triple: [V-bomber force, VulcanRole, delta-wing high-altitude bomber]
-
A.
roleInTauris
Indicates that an entity has a specific role or function within the context of Tauris (e.g., a work, setting, or domain associated with Tauris).
-
B.
MaadimVallisRole
Indicates that something serves as or is characterized by the functional role or significance of Maadim Vallis within a broader system, context, or process.
-
C.
roleInAlienCovenant
Indicates that an entity has a role or participation in the film "Alien: Covenant."
-
D.
roleInElysium
Indicates that an entity holds a specific role, position, or function within the context of Elysium.
-
E.
roleInNebula
Indicates that an entity holds a specific function, position, or involvement within a particular nebula.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:26 p.m.