Triple
T20285331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ralph |
E509860
|
entity |
| Predicate | conflictTypeWithJack |
P1397
|
FINISHED |
| Object | Struggle between civilization and savagery |
—
|
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: Struggle between civilization and savagery | Statement: [Ralph, conflictTypeWithJack, Struggle between civilization and savagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictTypeWithJack Context triple: [Ralph, conflictTypeWithJack, Struggle between civilization and savagery]
-
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.
conflictTypeManaged
Indicates that a conflict has been addressed or handled through some form of management or resolution process.
-
D.
conflictTypeLed
Indicates that one type or category of conflict directly resulted in, triggered, or gave rise to another specified outcome or situation.
-
E.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
- 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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e676924f48819095f6224c8d9bb257 |
completed | April 20, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:05 a.m.