Triple
T36362821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paxton |
E895539
|
entity |
| Predicate | facesConflictType |
P1397
|
FINISHED |
| Object | life-or-death struggle |
—
|
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: life-or-death struggle | Statement: [Paxton, facesConflictType, life-or-death struggle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facesConflictType Context triple: [Paxton, facesConflictType, life-or-death struggle]
-
A.
facesConflictWith
Indicates that one entity is in opposition, dispute, or contention with another, involving incompatible goals, interests, or actions.
-
B.
featuresConflictType
Indicates that there is a specific type or category of conflict between the features or characteristics of the related entities.
-
C.
conflictType
chosen
Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
-
D.
framesConflictAs
Indicates that one entity presents or interprets a situation, issue, or interaction specifically in terms of conflict or opposition between parties.
-
E.
holderConflict
Indicates a relationship where the current holder or possessor of something is in conflict or dispute over that holding, such as ownership, control, or rights.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:10 p.m.