Triple
T34640354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elvenking |
E889537
|
entity |
| Predicate | inUniverseForest |
P185986
|
FINISHED |
| Object | Great Forest of Mirkwood |
—
|
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: Great Forest of Mirkwood | Statement: [Elvenking, inUniverseForest, Great Forest of Mirkwood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseForest Context triple: [Elvenking, inUniverseForest, Great Forest of Mirkwood]
-
A.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
B.
inUniverseSea
Indicates that one entity exists or is located within the sea or oceanic environment of a specified fictional or defined universe.
-
C.
inUniverseStar
Indicates that a star exists or is located within a particular fictional or defined universe.
-
D.
inUniverseUse
Indicates that something is used or occurs within a particular fictional or conceptual universe, as opposed to in the real world or another setting.
-
E.
inUniverseReference
Indicates that one entity makes a reference to another entity that exists within the same fictional or conceptual universe.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 1, 2026, 2:04 a.m.