Triple
T35187150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fifi |
E1016020
|
entity |
| Predicate | partnerInFantasyOf |
P183168
|
FINISHED |
| Object | Snoopy |
—
|
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: Snoopy | Statement: [Fifi, partnerInFantasyOf, Snoopy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInFantasyOf Context triple: [Fifi, partnerInFantasyOf, Snoopy]
-
A.
partnerInSeries
Indicates that two entities are co-participants or collaborators within the same series, jointly contributing to or appearing in that ongoing sequence.
-
B.
partnerInMyth
Indicates a mythological relationship in which two entities are partners or companions within the same myth or mythic narrative.
-
C.
partnerInCompetition
Indicates that two or more entities are collaborating as partners or teammates within the same competitive event or context.
-
D.
partnerInLoveTeam
Indicates that two entities are teammates who are also partners in a romantic or love-based relationship.
-
E.
partnerInBattle
Indicates that two entities are allied or cooperate as partners in the same battle or combat engagement.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f798387ea481909f51303f53a22e52 |
completed | May 3, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79798663481908d6bc48dd6a94ca6 |
completed | May 3, 2026, 6:44 p.m. |
Created at: May 3, 2026, 4:02 p.m.