Triple
T17614269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Útgarðr |
E429041
|
entity |
| Predicate | boundaryRelation |
P37800
|
FINISHED |
| Object | outside the ordered enclosure of human civilization |
—
|
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: outside the ordered enclosure of human civilization | Statement: [Útgarðr, boundaryRelation, outside the ordered enclosure of human civilization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundaryRelation Context triple: [Útgarðr, boundaryRelation, outside the ordered enclosure of human civilization]
-
A.
hasBorderRelation
chosen
Indicates that one entity shares a boundary or border with another entity.
-
B.
adminBoundaryRelation
Indicates a relationship where one entity defines, delimits, or is associated with the administrative boundary of another entity.
-
C.
datumRelation
Indicates a relationship where one piece of data is connected to, derived from, or otherwise associated with another piece of data.
-
D.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
E.
relatedBorder
Indicates that two geographic or political entities share a common boundary or border with each other.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d2fd96481908c9f3b566fca6907 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.