Triple
T26391853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L’Ours |
E663431
|
entity |
| Predicate | notableBearActor |
P197691
|
FINISHED |
| Object | Bart the Bear |
—
|
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: Bart the Bear | Statement: [L’Ours, notableBearActor, Bart the Bear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBearActor Context triple: [L’Ours, notableBearActor, Bart the Bear]
-
A.
notableStarName
Indicates that the subject is known by the specified star name as a notable or prominent designation.
-
B.
notableStar
Indicates that the subject is a star (or stellar object) that is distinguished or noteworthy in some significant way, such as brightness, fame, or scientific interest, relative to other stars.
-
C.
notableCastMember
Indicates that an entity is a member of the cast of another entity (such as a film, show, or production) and is considered particularly notable or significant in that role.
-
D.
notableHuman
Indicates that the subject is a human who is recognized as notable or significant in some context.
-
E.
notableSeriesCharacter
Indicates that an entity is a significant or well-known character appearing in a particular 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
| PDg | Predicate description generation | batch_69fea2cfcd648190a15e5b90889095b1 |
completed | May 9, 2026, 2:58 a.m. |
Created at: April 26, 2026, 11:26 p.m.