Triple
T33582076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharkey the Bounty Hunter |
E860173
|
entity |
| Predicate | featuresAlienWorlds |
P76995
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sharkey the Bounty Hunter, featuresAlienWorlds, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresAlienWorlds Context triple: [Sharkey the Bounty Hunter, featuresAlienWorlds, yes]
-
A.
featuresAlien
Indicates that something includes, presents, or prominently involves an alien or extraterrestrial being.
-
B.
featuresUniverse
chosen
Indicates that one entity includes, presents, or prominently showcases a particular universe or world as part of its content or structure.
-
C.
featuresParallelUniverse
Indicates that the subject includes, involves, or prominently depicts a parallel or alternate universe in relation to its primary setting or reality.
-
D.
hasAlienSpecies
Indicates that one entity possesses, contains, or is associated with a particular alien species.
-
E.
alienSpecies
Indicates that one entity is a species that is foreign or not native to the other entity’s environment, context, or origin.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01cb89ff448190b60ee3d148ce76fc |
completed | May 11, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a01ca7604b48190bb8643c17c3a8c85 |
completed | May 11, 2026, 12:24 p.m. |
Created at: May 1, 2026, 1:40 a.m.