Triple
T25469135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bloodline Feud |
E638253
|
entity |
| Predicate | collectsWork |
P136157
|
FINISHED |
| Object | The Family Trade |
—
|
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: The Family Trade | Statement: [The Bloodline Feud, collectsWork, The Family Trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectsWork Context triple: [The Bloodline Feud, collectsWork, The Family Trade]
-
A.
workCollectedBy
chosen
Indicates that a created work has been gathered, acquired, or included within a collection maintained by another entity.
-
B.
coordinatesWorkOf
Indicates overseeing and organizing the tasks, efforts, or activities of others to ensure they work together effectively toward a common goal.
-
C.
workCollectionTitle
Indicates the title assigned to a collection of works associated with an entity.
-
D.
distributedWorksOf
Indicates that one entity disseminated, circulated, or handed out the works (such as creations, products, or materials) of another entity.
-
E.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 2:21 p.m.