Triple
T32285231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lollipop Guild |
E824811
|
entity |
| Predicate | memberOfFictionalRace |
P75242
|
FINISHED |
| Object | Munchkins |
—
|
NE NERFINISHED |
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: Munchkins | Statement: [The Lollipop Guild, memberOfFictionalRace, Munchkins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberOfFictionalRace Context triple: [The Lollipop Guild, memberOfFictionalRace, Munchkins]
-
A.
associatedWithFictionalGroup
Indicates that an entity has a connection or affiliation with a fictional group, organization, or collective.
-
B.
belongsToFictionalRegion
Indicates that an entity is located within, associated with, or under the jurisdiction of a fictional or imaginary geographic region.
-
C.
partOfFictionalGroup
chosen
Indicates that an entity belongs to or is a member of a specific fictional group, organization, or team.
-
D.
raceInLegendarium
Indicates that an entity belongs to a particular fictional race or species within a specific mythological or fantasy legendarium.
-
E.
usedByFictionalGroup
Indicates that something is utilized or employed by a fictional group or organization within a narrative context.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 1, 2026, 12:43 a.m.