Triple
T639577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strategic Defense Initiative |
E16701
|
entity |
| Predicate | raisedConcernAbout |
P17598
|
FINISHED |
| Object | compliance with Anti-Ballistic Missile Treaty |
—
|
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: compliance with Anti-Ballistic Missile Treaty | Statement: [Strategic Defense Initiative, raisedConcernAbout, compliance with Anti-Ballistic Missile Treaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raisedConcernAbout Context triple: [Strategic Defense Initiative, raisedConcernAbout, compliance with Anti-Ballistic Missile Treaty]
-
A.
concern
Indicates that one entity is about, relates to, or is of interest or importance to another entity.
-
B.
concernsRight
Indicates that something is about or relates specifically to a legal or moral right held by an entity.
-
C.
raisesQuestion
Indicates that one entity causes or prompts a question or doubt to arise about another entity or topic.
-
D.
concernsLayer
Indicates that something is related or pertains specifically to a particular layer within a layered structure or system.
-
E.
hasHealthConcern
Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f00260081909d1a679182e23d10 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0830008190a26ee158ed4dd1fe |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49df0de3c81909721eb391ec94031 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.