Triple
T20907949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christine |
E514855
|
entity |
| Predicate | conflictTypeWithHeed |
P1397
|
FINISHED |
| Object | competition |
—
|
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: competition | Statement: [Christine, conflictTypeWithHeed, competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictTypeWithHeed Context triple: [Christine, conflictTypeWithHeed, competition]
-
A.
conflictType
chosen
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
B.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
-
C.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
D.
conflictTypeLed
Indicates that one type or category of conflict directly resulted in, triggered, or gave rise to another specified outcome or situation.
-
E.
conflictIntended
Indicates that one entity deliberately aims to oppose, obstruct, or create conflict with another entity or its goals.
- 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e900ee7881909ab1046b40dca486 |
completed | April 21, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:47 p.m.