Triple
T15490136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hell of the North |
E378659
|
entity |
| Predicate | refersToConditions |
P115374
|
FINISHED |
| Object | muddy conditions |
—
|
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: muddy conditions | Statement: [Hell of the North, refersToConditions, muddy conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToConditions Context triple: [Hell of the North, refersToConditions, muddy conditions]
-
A.
definesConditionsFor
Indicates that one entity specifies or establishes the rules, requirements, or circumstances under which another entity is valid, applicable, or operates.
-
B.
refersSpecificallyTo
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
-
C.
alsoRefersTo
Indicates that one term, label, or identifier is used as an alternative designation for the same entity or concept as another.
-
D.
referredTo
chosen
Indicates that one entity has mentioned, directed attention to, or cited another entity as a point of reference.
-
E.
refersToAction
Indicates that one entity explicitly points to, mentions, or designates a specific action or event.
- 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.