Triple
T29188361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-canon (pre-2014 Lucasfilm canon hierarchy) |
E739929
|
entity |
| Predicate | conflictsResolvedBy |
P23081
|
FINISHED |
| Object | G-canon |
—
|
NE NERFINISHED |
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: G-canon | Statement: [C-canon (pre-2014 Lucasfilm canon hierarchy), conflictsResolvedBy, G-canon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictsResolvedBy Context triple: [C-canon (pre-2014 Lucasfilm canon hierarchy), conflictsResolvedBy, G-canon]
-
A.
conflictResolvedBy
chosen
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
-
B.
conflictedOverBy
Indicates that one entity is the subject of conflict, dispute, or contention initiated or experienced by another entity.
-
C.
conflictedBetween
Indicates being torn or uncertain between two or more options, positions, or commitments.
-
D.
conflictResult
Indicates the outcome or consequence that arises from a particular conflict between entities.
-
E.
addressedConflictWith
Indicates that one entity has taken action to confront, manage, or resolve a conflict involving another entity.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 12:01 p.m.