Triple
T28273219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spirit Realm (Kung Fu Panda) |
E712910
|
entity |
| Predicate | usedByProtagonist |
P31799
|
FINISHED |
| Object | Po to master chi |
—
|
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: Po to master chi | Statement: [Spirit Realm (Kung Fu Panda), usedByProtagonist, Po to master chi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByProtagonist Context triple: [Spirit Realm (Kung Fu Panda), usedByProtagonist, Po to master chi]
-
A.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
C.
usedByCharacter
chosen
Indicates that something (such as an item, ability, or resource) is utilized or employed by a particular character.
-
D.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
E.
hasChildProtagonist
Indicates that the work features a child as its main or central character.
- F. None of above.
Provenance (3 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 11:18 p.m.