Triple
T25475091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grail |
E638409
|
entity |
| Predicate | roleOfSystem |
P12085
|
FINISHED |
| Object | short-range air defense |
—
|
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: short-range air defense | Statement: [Grail, roleOfSystem, short-range air defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfSystem Context triple: [Grail, roleOfSystem, short-range air defense]
-
A.
roleOfCharacter
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
-
B.
systemRole
chosen
Indicates the functional position or responsibility that an entity holds within a larger system or structure.
-
C.
roleInGemini3
Indicates that an entity holds a specific role or function within the Gemini 3 mission or project.
-
D.
designedRole
Indicates that one entity has been created, configured, or intended to serve a particular function, purpose, or role in relation to another entity.
-
E.
roleInGemini10
Indicates that an entity holds a specific role or position in the context of the Gemini 10 mission or project.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f754447c8190acc16c440f8bb03d |
completed | May 2, 2026, 1:08 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:25 p.m.