Triple
T10387296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DreamWorks Theatre Featuring Kung Fu Panda |
E244794
|
entity |
| Predicate | featuresCharacter |
P626
|
FINISHED |
| Object | Po |
E683351
|
NE 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 | Statement: [DreamWorks Theatre Featuring Kung Fu Panda, featuresCharacter, Po]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Po Context triple: [DreamWorks Theatre Featuring Kung Fu Panda, featuresCharacter, Po]
-
A.
Po
The Po is Italy’s longest and most important river, flowing eastward across northern Italy from the Alps to the Adriatic Sea.
-
B.
Po
chosen
Po is the lovable, dumpling-obsessed panda who becomes the Dragon Warrior and hero of the Kung Fu Panda film series.
-
C.
PO
PO is a UK postcode area covering Portsmouth and surrounding parts of Hampshire and West Sussex.
-
D.
PO
PO is the commonly used abbreviation for Opole University of Technology, a technical university located in Opole, Poland.
-
E.
Pu
Pu is a Chinese surname historically borne by various notable figures and families in China.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9a4e6748190bd9dd319de94c659 |
completed | April 7, 2026, 11:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d795aa3afc8190aed1ca11556ae34f |
completed | April 9, 2026, 12:03 p.m. |
Created at: April 6, 2026, 12:05 p.m.