Triple
T37460488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sludge Belcher |
E930903
|
entity |
| Predicate | hasOriginalSetType |
P199160
|
FINISHED |
| Object | Adventure-exclusive |
—
|
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: Adventure-exclusive | Statement: [Sludge Belcher, hasOriginalSetType, Adventure-exclusive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalSetType Context triple: [Sludge Belcher, hasOriginalSetType, Adventure-exclusive]
-
A.
hasOriginalFeature
Indicates that an entity possesses a feature or characteristic in its initial, unmodified, or native form.
-
B.
hasOriginalWorkSetting
Indicates that an entity is associated with the setting or context in which the original work or source material takes place.
-
C.
hasOriginalRole
Indicates that an entity previously held a particular role or function before a change to its current role.
-
D.
hasSettlementTypeOrigin
Indicates that an entity’s settlement type is derived from, or originates in, a specified source or origin.
-
E.
hasOriginalComposition
Indicates that one entity is the initial or primary compositional source or makeup of another 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69ff234e63648190a7b09a161029c8e2 |
completed | May 9, 2026, 12:06 p.m. |
Created at: May 3, 2026, 4:17 p.m.