Triple
T33699723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Table Manners |
E863420
|
entity |
| Predicate | followsSameEventsAs |
P132447
|
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, followsSameEventsAs, Living Together]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsSameEventsAs Context triple: [Table Manners, followsSameEventsAs, Living Together]
-
A.
eventFollowedBy
Indicates that one event occurs after and in sequence with another event.
-
B.
followsCalendarOf
Indicates that one entity adopts and adheres to the scheduling, events, or time structure defined by another entity’s calendar.
-
C.
isFollowedAcrossYearsBy
Indicates that one entity’s occurrence or validity in time is directly succeeded by another entity’s occurrence or validity in subsequent years.
-
D.
sharesCeremoniesWith
chosen
Indicates that two entities participate in or observe the same ceremonies or ritual practices.
-
E.
followerEvent
Indicates that one entity begins or performs the action of following another entity, typically recorded as a discrete event in time.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: May 1, 2026, 1:43 a.m.