Triple
T28374812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Animation Academy |
E718727
|
entity |
| Predicate | guestParticipation |
P33356
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Animation Academy, guestParticipation, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guestParticipation Context triple: [Animation Academy, guestParticipation, high]
-
A.
participantCustom
Indicates that an entity participates in an event, activity, or process in a role or manner that is defined in a customized or non-standard way.
-
B.
invitesParticipationOf
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
-
C.
eventParticipant
chosen
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
D.
participantFrom
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
-
E.
participantMayAlsoContributeTo
Indicates that an entity participating in something is additionally allowed or able to contribute to it in some way.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c5d1290819087cbb832239699d4 |
completed | May 2, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:02 a.m.