Triple
T37378387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paths of the Dead |
E928358
|
entity |
| Predicate | entersAt |
P154866
|
FINISHED |
| Object | Dimholt |
—
|
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: Dimholt | Statement: [Paths of the Dead, entersAt, Dimholt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entersAt Context triple: [Paths of the Dead, entersAt, Dimholt]
-
A.
entersBy
Indicates that one entity moves into or gains access to another entity through a specified entrance, route, or means.
-
B.
enteredAt
chosen
Indicates the time or place at which an entity entered or was recorded as entering a particular context, system, or location.
-
C.
entersFrom
Indicates that one entity moves into or arrives at a place, state, or context by coming from another specified source or location.
-
D.
enteredIn
Indicates that one entity has gone into, been placed into, or become included within another entity, such as a space, container, system, or context.
-
E.
entersTimeline
Indicates that an entity begins to appear or be included at a specific point within a timeline or chronological sequence.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:16 p.m.