Triple
T33582077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharkey the Bounty Hunter |
E860173
|
entity |
| Predicate | featuresBountyHunting |
P30868
|
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, featuresBountyHunting, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresBountyHunting Context triple: [Sharkey the Bounty Hunter, featuresBountyHunting, yes]
-
A.
featuresTreasureHunt
Indicates that something includes or offers a treasure hunt activity or experience.
-
B.
bounty
chosen
Indicates that a reward or payment is offered for performing a specific action or achieving a particular outcome related to an entity.
-
C.
featuresDemon
Indicates that an entity includes, depicts, or prominently involves a demon.
-
D.
featuresAward
Indicates that something includes, presents, or highlights a particular award as part of its content or attributes.
-
E.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01ccd995e48190b6675e463bd0a567 |
completed | May 11, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_6a01cc33177c8190bc0703276618b3ec |
completed | May 11, 2026, 12:31 p.m. |
Created at: May 1, 2026, 1:40 a.m.