Triple
T10660938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dassault Mirage IV |
E251220
|
entity |
| Predicate | roleOfMirageIVA |
P95201
|
FINISHED |
| Object | free‑fall nuclear 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: free‑fall nuclear bomber | Statement: [Dassault Mirage IV, roleOfMirageIVA, free‑fall nuclear bomber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfMirageIVA Context triple: [Dassault Mirage IV, roleOfMirageIVA, free‑fall nuclear bomber]
-
A.
roleInIR8
Indicates that an entity plays a specific role or function within the IR8 context (e.g., the IR8 rice variety or related initiative).
-
B.
MiramboRole
Indicates that an entity holds a specific role, position, or function in relation to Mirambo.
-
C.
primaryMirrorConfiguration
Indicates the specific structural and optical setup used for a system’s primary mirror.
-
D.
describesRoleAs
Indicates that one entity specifies or characterizes the role or function played by another entity.
-
E.
roleInIntegration
Indicates the specific function or responsibility an entity has within a combined or coordinated system, process, or integration.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6e017f97c8190b22765a6f1e6719d |
completed | April 8, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df47899481909ac0e518d94883cb |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 9:08 p.m.