Triple
T6543109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strategic Arms Reduction Treaty |
E168337
|
entity |
| Predicate | implementationStart |
P72290
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Strategic Arms Reduction Treaty, implementationStart, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementationStart Context triple: [Strategic Arms Reduction Treaty, implementationStart, 1994]
-
A.
operationStart
Indicates the point in time or event at which a specific operation or process begins.
-
B.
developmentStart
Indicates the point in time or event when the development process of something begins.
-
C.
implementationStatus
Indicates the current state or progress of carrying out or realizing something, such as a plan, design, or requirement.
-
D.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
E.
implementedOn
Indicates that something (such as a feature, standard, or specification) is realized, executed, or put into effect within or on a particular platform, system, or environment.
- 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_69c68a51564081909e93aee0dbd9cca3 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6ce0538f48190abf3160681901c17 |
completed | March 27, 2026, 6:35 p.m. |
Created at: March 27, 2026, 1:50 p.m.