Triple
T20865305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross Creek |
E513744
|
entity |
| Predicate | hasCommonConflictType |
P68124
|
FINISHED |
| Object | personal grudges |
—
|
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: personal grudges | Statement: [Cross Creek, hasCommonConflictType, personal grudges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonConflictType Context triple: [Cross Creek, hasCommonConflictType, personal grudges]
-
A.
hasPrimaryConflictType
chosen
Indicates that an entity is associated with its main or most significant type of conflict among possible conflict categories.
-
B.
hasRelatedConflict
Indicates that one entity is associated with another entity through a related or connected conflict, dispute, or incompatibility.
-
C.
hasConflictCause
Indicates that one entity is the cause or source of a conflict involving another entity.
-
D.
hasConflictStatus
Indicates that there exists a state of conflict or dispute associated with the relationship between the involved entities.
-
E.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c45fbfc88190914c5133aa4b242c |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.