Triple
T34103595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schraderbräu |
E874639
|
entity |
| Predicate | servedToCharacter |
P200322
|
FINISHED |
| Object | Walter White |
—
|
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: Walter White | Statement: [Schraderbräu, servedToCharacter, Walter White]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedToCharacter Context triple: [Schraderbräu, servedToCharacter, Walter White]
-
A.
servedBefore
Indicates that one entity was served prior to another in time or sequence.
-
B.
servedWith
Indicates that one item is customarily presented, provided, or consumed together with another as an accompaniment or side.
-
C.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
D.
intendedToServe
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another entity.
-
E.
served
Indicates that one entity provided a service, assistance, or role-based function to or for another entity.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
| PDg | Predicate description generation | batch_69ff80d8ff208190b9e95d077fd99f78 |
completed | May 9, 2026, 6:45 p.m. |
Created at: May 1, 2026, 1:53 a.m.