Triple
T5766898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-short |
E127236
|
entity |
| Predicate | wasKeyIn |
P7606
|
FINISHED |
| Object | discovery of CP violation |
—
|
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: discovery of CP violation | Statement: [K-short, wasKeyIn, discovery of CP violation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasKeyIn Context triple: [K-short, wasKeyIn, discovery of CP violation]
-
A.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
B.
isKeyPostIn
Indicates that a post or position is a central, strategically important element within a specified organization, structure, or context.
-
C.
key
chosen
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
D.
wasLast
Indicates that one entity occurred or appeared after all others in a sequence, making it the final item or event.
-
E.
wasA
Indicates that an entity previously had a certain role, type, or classification in the past.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.