Triple
T23590388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert Sullivan |
E582459
|
entity |
| Predicate | servedTogetherWith |
P152828
|
FINISHED |
| Object | George Thomas Sullivan |
—
|
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: George Thomas Sullivan | Statement: [Albert Sullivan, servedTogetherWith, George Thomas Sullivan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedTogetherWith Context triple: [Albert Sullivan, servedTogetherWith, George Thomas Sullivan]
-
A.
servedWith
Indicates that one item is customarily presented, provided, or consumed together with another as an accompaniment or side.
-
B.
servesWith
Indicates that one entity is customarily presented, used, or consumed together with another as a complementary accompaniment.
-
C.
isTypicallyEatenWith
Indicates that one item is commonly consumed together with another as part of the same eating occasion or dish.
-
D.
servesDish
Indicates that one entity prepares and presents a specific dish as food for another entity.
-
E.
alsoServes
Indicates that an entity, in addition to its primary role or function, provides service or support to another specified entity or group.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b03484e4819093d5c14c891f7744 |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:42 p.m.