Triple
T38093058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HypnoMagic |
E951165
|
entity |
| Predicate | appliedToWork |
P181162
|
FINISHED |
| Object | The Hypnotic Eye |
—
|
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: The Hypnotic Eye | Statement: [HypnoMagic, appliedToWork, The Hypnotic Eye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToWork Context triple: [HypnoMagic, appliedToWork, The Hypnotic Eye]
-
A.
appliedToWorkBy
Indicates that an application or request has been submitted by a person or entity for a particular job, project, or work opportunity.
-
B.
appliesToWork
Indicates that something (such as a rule, policy, condition, or attribute) is relevant to, governs, or is in effect for a particular piece of work or work-related activity.
-
C.
appliedWork
Indicates that an entity has put effort, skill, or labor into performing or producing a particular work or task.
-
D.
appliedToWorkCurrentLocation
Indicates that an application was submitted for a job or position at the entity’s current work location.
-
E.
usedForWork
chosen
Indicates that something is employed or utilized to perform tasks, duties, or activities related to a job or occupation.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: May 3, 2026, 4:21 p.m.