Triple
T33699740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Table Manners |
E863420
|
entity |
| Predicate | hasTrilogyCompanionPlay |
P199561
|
FINISHED |
| Object | Living Together |
—
|
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: Living Together | Statement: [Table Manners, hasTrilogyCompanionPlay, Living Together]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrilogyCompanionPlay Context triple: [Table Manners, hasTrilogyCompanionPlay, Living Together]
-
A.
hasTrilogy
Indicates that an entity is part of, or associated with, a specific trilogy within a larger set of works or narratives.
-
B.
hasTrilogyCompanionWorkEnglish
Indicates that an English-language work is associated with another work as part of a trilogy companion relationship.
-
C.
hasPartInTrilogy
Indicates that an entity is one of the constituent parts (e.g., books, films, or episodes) that together form a specific trilogy.
-
D.
hasSequelInTrilogy
Indicates that one work in a trilogy is followed by another work that serves as its sequel within that same three-part series.
-
E.
hasCompanionFilm
Indicates that one film is officially paired with another as a companion work, intended to be viewed or understood together.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff45793d5c81909dc503ad1f714ee2 |
completed | May 9, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69ff41cb0e088190a6e9b03cb20e5fad |
completed | May 9, 2026, 2:16 p.m. |
| PDg | Predicate description generation | batch_69ff45782cb88190b604811e4d724382 |
completed | May 9, 2026, 2:32 p.m. |
Created at: May 1, 2026, 1:43 a.m.