Triple
T15490134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hell of the North |
E378659
|
entity |
| Predicate | refersToSurface |
P34471
|
FINISHED |
| Object | cobblestone roads |
—
|
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: cobblestone roads | Statement: [Hell of the North, refersToSurface, cobblestone roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToSurface Context triple: [Hell of the North, refersToSurface, cobblestone roads]
-
A.
usesSurface
Indicates that one entity employs or interacts with another entity as a surface or platform for its action or function.
-
B.
targetSurface
Indicates the surface or area that an action, effect, or object is directed at or intended to impact.
-
C.
notableSurface
chosen
Indicates that one entity is a surface or exterior of particular significance or prominence in relation to another entity.
-
D.
referenceSurface
Indicates that one entity serves as the surface or base relative to which another entity is positioned, aligned, or defined.
-
E.
hasSurfaceLevel
Indicates that one entity possesses or is characterized by a particular degree or measure of surface level (e.g., depth, detail, or superficiality).
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fac2af88190ac1d119e6b21dbe0 |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:48 a.m.