Triple
T7642777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Evil Queen |
E173047
|
entity |
| Predicate | killsByProxy |
P77493
|
FINISHED |
| Object | huntsman |
—
|
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: huntsman | Statement: [The Evil Queen, killsByProxy, huntsman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killsByProxy Context triple: [The Evil Queen, killsByProxy, huntsman]
-
A.
kills
Indicates that one entity causes the death of another entity, ending its life.
-
B.
skillSet
Indicates that an entity possesses or is associated with a particular collection of skills or competencies.
-
C.
hasEponymousSkill
Indicates that an entity possesses a skill that is named after a particular person or entity.
-
D.
requiresSkill
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
-
E.
skillAssessed
Indicates that an entity’s skill or competency has been evaluated or measured, typically by another agent or process.
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faef96908190a7724b204f9d8c9e |
completed | March 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f574d8a8819095749518dad13791 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:58 p.m.