Triple
T34403642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Creek |
E883048
|
entity |
| Predicate | hasOppressorInFiction |
P188914
|
FINISHED |
| Object | mining baron |
—
|
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: mining baron | Statement: [Rose Creek, hasOppressorInFiction, mining baron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOppressorInFiction Context triple: [Rose Creek, hasOppressorInFiction, mining baron]
-
A.
hasFictionalWork
Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
-
B.
hasFictionalAuthor
Indicates that one entity is the fictional or in-universe author of a work attributed to them.
-
C.
hasViewOfFictional
Indicates that one entity has a visual or conceptual perspective of a fictional entity or scene.
-
D.
hasEthnicityInFiction
Indicates that a fictional character or entity is portrayed as having a particular ethnicity within a narrative or fictional context.
-
E.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: May 1, 2026, 1:59 a.m.