Triple
T33912714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaws (James Bond character) |
E869360
|
entity |
| Predicate | roleInMoonraker |
P202717
|
FINISHED |
| Object | henchman of Hugo Drax |
—
|
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: henchman of Hugo Drax | Statement: [Jaws (James Bond character), roleInMoonraker, henchman of Hugo Drax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMoonraker Context triple: [Jaws (James Bond character), roleInMoonraker, henchman of Hugo Drax]
-
A.
roleInCitadel
Indicates the specific function, position, or responsibility an entity holds within a citadel or fortified complex.
-
B.
roleInMATE
Indicates that an entity participates in a MATE (Modeling and Analysis of Telecommunication Systems) context with a specific functional or contextual role.
-
C.
roleInManiacMansion
Indicates that an entity has a specific role or part in the game *Maniac Mansion*.
-
D.
roleInSense8
Indicates that one entity has a specific acting or production role in the TV series "Sense8" in relation to another entity.
-
E.
roleInWatchmen
Indicates that one entity has a specific role or function within the context of the work "Watchmen" in relation to the other entity.
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00af6b3a948190a92813c13384c304 |
completed | May 10, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_6a00aec35610819085dd5137715a4228 |
completed | May 10, 2026, 4:13 p.m. |
| PDg | Predicate description generation | batch_6a00af6a5ffc819095c7331518a09f53 |
completed | May 10, 2026, 4:16 p.m. |
Created at: May 1, 2026, 1:48 a.m.