Triple
T2953902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strategic Defense Initiative |
E79884
|
entity |
| Predicate | nickNameGivenBy |
P44320
|
FINISHED |
| Object | critics |
—
|
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: critics | Statement: [Strategic Defense Initiative, nickNameGivenBy, critics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nickNameGivenBy Context triple: [Strategic Defense Initiative, nickNameGivenBy, critics]
-
A.
mediaNicknameGivenBy
Indicates that a particular nickname was assigned to an entity by media organizations or outlets.
-
B.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
C.
localNickname
Indicates that an entity is known by a particular nickname within a specific local or regional context.
-
D.
fandomNickname
Indicates that one entity is the nickname used by fans to refer to another entity (such as a person, group, or work).
-
E.
reasonForNickname
Indicates the explanation or cause behind why a particular nickname was given to an entity.
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98ff874c81908077a90fdc5e8549 |
completed | March 8, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:57 p.m.