Triple
T24946254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waa |
E624190
|
entity |
| Predicate | associatedWithRoleInStories |
P42552
|
FINISHED |
| Object | trickster |
—
|
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: trickster | Statement: [Waa, associatedWithRoleInStories, trickster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRoleInStories Context triple: [Waa, associatedWithRoleInStories, trickster]
-
A.
associatedWithPersonInStory
Indicates that one entity has a connection or involvement with a specific person within the context of a story.
-
B.
roleInStories
chosen
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
C.
hasStaffTypeInStory
Indicates that a story involves or is associated with a particular type or category of staff.
-
D.
associatedWithAuthorRole
Indicates that an entity is connected to another entity specifically in the capacity or role of an author.
-
E.
associatedTale
Indicates that one entity is linked or connected to a particular tale, story, or narrative.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 18, 2026, 5:54 a.m.