Triple
T15213046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miðgarðr |
E363564
|
entity |
| Predicate | hasBoundaryFunction |
P97842
|
FINISHED |
| Object | defensive enclosure against chaos |
—
|
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: defensive enclosure against chaos | Statement: [Miðgarðr, hasBoundaryFunction, defensive enclosure against chaos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoundaryFunction Context triple: [Miðgarðr, hasBoundaryFunction, defensive enclosure against chaos]
-
A.
hasBorderFunctionWith
chosen
Indicates a relationship where one entity serves a boundary-related role or function in conjunction with another entity.
-
B.
hasBoundaryCriterion
Indicates that something is associated with a specific rule or condition used to define or limit its boundary.
-
C.
hasBoundaryFeature
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
D.
hasBoundaryShape
Indicates that an entity is associated with, or characterized by, a specific geometric or spatial shape of its boundary.
-
E.
hasBoundaryType
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0076c9e2481909d7a464b2172f4bf |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:11 a.m.