Triple
T1434590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris Summit of 1960 |
E30530
|
entity |
| Predicate | hasMainIssue |
P12603
|
FINISHED |
| Object | nuclear arms control |
—
|
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: nuclear arms control | Statement: [Paris Summit of 1960, hasMainIssue, nuclear arms control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainIssue Context triple: [Paris Summit of 1960, hasMainIssue, nuclear arms control]
-
A.
hasNotableIssue
Indicates that an entity is associated with a significant problem, concern, or defect that is noteworthy or exceptional compared to typical cases.
-
B.
hasKeyIssue
chosen
Indicates that an entity is associated with a primary or central problem, concern, or topic of importance.
-
C.
majorIssue
Indicates that something is a primary or most significant problem, concern, or obstacle in a given context.
-
D.
hasTargetIssue
Indicates that an entity is associated with or directed toward a specific issue, problem, or concern as its focus.
-
E.
hasMainOrgan
Indicates that an entity possesses a primary or principal organ that plays a central role in its biological or functional 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c478f65481909ee716791c663491 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.