Triple
T22746077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leprechaun Legion |
E562557
|
entity |
| Predicate | hasCheeringActivities |
P18289
|
FINISHED |
| Object | chants |
—
|
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: chants | Statement: [Leprechaun Legion, hasCheeringActivities, chants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheeringActivities Context triple: [Leprechaun Legion, hasCheeringActivities, chants]
-
A.
hasCheerStyle
Indicates that an entity possesses or is associated with a particular style or manner of cheering.
-
B.
hasCheerleaders
Indicates that an entity is associated with or supported by one or more cheerleaders.
-
C.
hasInGameActivities
Indicates that an entity includes or offers specific activities or actions that can be performed within a game context.
-
D.
hasFanActivity
chosen
Indicates that an entity is associated with actions, behaviors, or engagement carried out by fans in relation to it.
-
E.
hasAudienceParticipation
Indicates that an event, performance, or activity involves direct participation or interaction from the audience.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179b563e481908804d07fca1777b9 |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:24 p.m.