Triple
T6044984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesje |
E134643
|
entity |
| Predicate | hasInnerConflict |
P20436
|
FINISHED |
| Object | questions of identity |
—
|
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: questions of identity | Statement: [Lesje, hasInnerConflict, questions of identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInnerConflict Context triple: [Lesje, hasInnerConflict, questions of identity]
-
A.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
-
B.
hasConflictStatus
Indicates that there exists a state of conflict or dispute associated with the relationship between the involved entities.
-
C.
hasRelatedConflict
Indicates that one entity is associated with another entity through a related or connected conflict, dispute, or incompatibility.
-
D.
internalConflict
chosen
Indicates a relationship where an entity experiences opposing desires, beliefs, or motives within itself, leading to psychological or emotional tension.
-
E.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
- 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_69c00876a69881908088a2626d3b2666 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056e41f98819089c205ba6138faf0 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049eb52a08190ac10fd703735f5aa |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.