Triple
T25475109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grail |
E638409
|
entity |
| Predicate | systemPrimaryUse |
P125948
|
FINISHED |
| Object | air defense for ground forces |
—
|
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: air defense for ground forces | Statement: [Grail, systemPrimaryUse, air defense for ground forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemPrimaryUse Context triple: [Grail, systemPrimaryUse, air defense for ground forces]
-
A.
systemUsedBy
Indicates that a particular system is utilized or operated by a specified agent or user.
-
B.
isPrimarilyUsedAs
chosen
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
-
C.
primaryDeviceCategory
Indicates the main type or class of device associated with an entity or event, distinguishing it from other possible device categories.
-
D.
terminal1PrimaryUse
Indicates the main or predominant function or purpose for which terminal 1 is used.
-
E.
usedBySystem
Indicates that something is utilized or operated by a particular system.
- 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_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 2:25 p.m.