Triple
T22768393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iris |
E563186
|
entity |
| Predicate | exploitedByCharacter |
P149659
|
FINISHED |
| Object | Sport |
—
|
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: Sport | Statement: [Iris, exploitedByCharacter, Sport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploitedByCharacter Context triple: [Iris, exploitedByCharacter, Sport]
-
A.
usedByCharacter
Indicates that something (such as an item, ability, or resource) is utilized or employed by a particular character.
-
B.
experiencedByCharacter
Indicates that a particular event, situation, or emotion is undergone or lived through by a specific character.
-
C.
employsFictionalCharacter
Indicates that one entity (typically an organization or individual) has hired or uses the services of a fictional character in some capacity.
-
D.
explainedByCharacter
Indicates that something (such as an event, situation, or piece of information) is explained or clarified by a particular character.
-
E.
discoveredByFictionalCharacter
Indicates that something (such as an object, place, or concept) is discovered by a fictional character within a narrative.
- 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b59c9cc8190a6edd68f3209a672 |
completed | April 29, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:27 p.m.