Triple
T38677741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danny Saunders |
E943802
|
entity |
| Predicate | conflictAbout |
P163904
|
FINISHED |
| Object | religious tradition |
—
|
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: religious tradition | Statement: [Danny Saunders, conflictAbout, religious tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictAbout Context triple: [Danny Saunders, conflictAbout, religious tradition]
-
A.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
B.
conflictTopic
chosen
Indicates that the entities are in conflict specifically regarding the referenced topic or issue.
-
C.
loreConflict
Indicates that there is an inconsistency, contradiction, or incompatibility between pieces of lore or canonical information.
-
D.
conflictSpecific
Indicates a specific, concrete instance or type of conflict that exists between the related entities.
-
E.
addressesConflictWithin
Indicates that one entity deals with, manages, or resolves a conflict that exists inside another entity or within its internal scope.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.