Triple
T27460651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conny Spalding |
E692729
|
entity |
| Predicate | sourceOfConflictIn |
P48690
|
FINISHED |
| Object | Two Can Play That Game |
—
|
NE NERFINISHED |
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: Two Can Play That Game | Statement: [Conny Spalding, sourceOfConflictIn, Two Can Play That Game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceOfConflictIn Context triple: [Conny Spalding, sourceOfConflictIn, Two Can Play That Game]
-
A.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
B.
conflictSource
chosen
Indicates that one entity is the origin, cause, or initiating side of a conflict involving another entity.
-
C.
originatingConflict
Indicates the conflict or dispute from which another event, situation, or relationship initially arises or is caused.
-
D.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
-
E.
hasCauseOfConflict
Indicates a relationship where one entity is the source or reason for a conflict involving another entity.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 12:50 p.m.