Triple
T28041099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tannen family |
E708541
|
entity |
| Predicate | recurringConflictWith |
P163655
|
FINISHED |
| Object | McFly family |
—
|
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: McFly family | Statement: [Tannen family, recurringConflictWith, McFly family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recurringConflictWith Context triple: [Tannen family, recurringConflictWith, McFly family]
-
A.
previousConflict
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
-
B.
mentionsConflict
Indicates that one entity refers to or discusses a dispute, disagreement, or conflict involving another entity.
-
C.
dateConflict
Indicates that two scheduled dates or time periods overlap or otherwise cannot both be accommodated without a clash.
-
D.
subsequentConflict
Indicates that one conflict occurs after and is temporally subsequent to another conflict.
-
E.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
- F. None of above. chosen
Provenance (4 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63f2fb6548190b187123a2250cea6 |
completed | May 2, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 8:25 p.m.