Triple
T32172563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valentine Bluffs |
E821749
|
entity |
| Predicate | hasFictionalMine |
P197931
|
FINISHED |
| Object | Hanniger Mine |
—
|
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: Hanniger Mine | Statement: [Valentine Bluffs, hasFictionalMine, Hanniger Mine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalMine Context triple: [Valentine Bluffs, hasFictionalMine, Hanniger Mine]
-
A.
hasFictionalContent
Indicates that something contains or includes material that is imaginary, invented, or not intended to represent real events or facts.
-
B.
hasFictionalProperty
Indicates that an entity possesses a property, attribute, or characteristic that exists only in a fictional or imaginary context.
-
C.
hasFictionalPet
Indicates that an entity has, owns, or is associated with a pet that is fictional or imaginary.
-
D.
hasFictionalScope
Indicates that something pertains to, applies within, or is limited to a fictional or imagined context rather than real-world scope.
-
E.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69feba0e362c81909883a3f24a4a9545 |
completed | May 9, 2026, 4:37 a.m. |
Created at: May 1, 2026, 12:33 a.m.