Triple
T14401140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratatoskr |
E357071
|
entity |
| Predicate | positionOnYggdrasil |
P3250
|
FINISHED |
| Object | trunk of the tree |
—
|
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: trunk of the tree | Statement: [Ratatoskr, positionOnYggdrasil, trunk of the tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnYggdrasil Context triple: [Ratatoskr, positionOnYggdrasil, trunk of the tree]
-
A.
positionRelativeToSummit
Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
-
B.
positionOnTerritory
Indicates that one entity occupies or is located at a specific position within the spatial extent of another entity’s territory.
-
C.
positionOnTreeOfLife
Indicates the relative placement of an entity within the evolutionary hierarchy or branching structure of the tree of life.
-
D.
positionOn
chosen
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
E.
positionInUnderworld
Indicates a hierarchical or role-based position that an entity holds within an underworld or criminal organization.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de908500048190bb6a20fe318d5c62 |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:17 a.m.