Triple
T12608123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ababeel missile |
E301035
|
entity |
| Predicate | publiclyKnownTests |
P41250
|
FINISHED |
| Object | limited |
—
|
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: limited | Statement: [Ababeel missile, publiclyKnownTests, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publiclyKnownTests Context triple: [Ababeel missile, publiclyKnownTests, limited]
-
A.
testsIn
Indicates that one entity conducts or performs tests within, on, or using another entity.
-
B.
establishedTest
Indicates that an entity has created, set up, or formally instituted a test or testing process.
-
C.
announcedTest
chosen
Indicates that an entity has formally communicated or made public the existence or details of a test.
-
D.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
-
E.
appliedTest
Indicates that a test has been administered or carried out on a particular subject or object.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:11 p.m.