Triple
T17945181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarah |
E448684
|
entity |
| Predicate | recurringCharacterInSeason |
P129830
|
FINISHED |
| Object | Ed, Edd n Eddy season 1 |
—
|
LITERAL FINISHED |
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: Ed, Edd n Eddy season 1 | Statement: [Sarah, recurringCharacterInSeason, Ed, Edd n Eddy season 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recurringCharacterInSeason Context triple: [Sarah, recurringCharacterInSeason, Ed, Edd n Eddy season 1]
-
A.
playedInSeason
Indicates that an entity (such as a player or participant) took part in or was active during a specific season.
-
B.
roleInSeason
Indicates the specific role or function an entity has within a particular season of a series or competition.
-
C.
hasRecurringSeriesProtagonists
Indicates that a recurring series features one or more protagonists who appear repeatedly across its installments.
-
D.
hasRecurringCharacterFrom
Indicates that one work or series includes a character who also appears recurrently in another work or series.
-
E.
hasRecurringProtagonists
Indicates that the same main character or set of main characters appears repeatedly across multiple works or installments in a series.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad990b948190a5e6fd50a15f64e3 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:21 a.m.