Triple
T34161842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hnitbjörg |
E876297
|
entity |
| Predicate | escapeRouteFor |
P140954
|
FINISHED |
| Object | Odin carrying the mead of poetry as an eagle |
—
|
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: Odin carrying the mead of poetry as an eagle | Statement: [Hnitbjörg, escapeRouteFor, Odin carrying the mead of poetry as an eagle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escapeRouteFor Context triple: [Hnitbjörg, escapeRouteFor, Odin carrying the mead of poetry as an eagle]
-
A.
avoidsRoute
Indicates that an entity deliberately does not use or travel along a particular route.
-
B.
exitRoutes
chosen
Indicates that there are designated paths or ways for entities to leave or move out from a particular place or situation.
-
C.
escapeLocation
Indicates that an entity moves away from or leaves a location to avoid danger, capture, or an undesirable situation.
-
D.
escapeBehavior
Indicates a relationship where an entity actively attempts to avoid, flee from, or get away from another entity, situation, or constraint.
-
E.
escapeOf
Indicates that one entity escapes, is released, or leaks out from another entity or containing 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fdedf708190ab68c2d567e086d0 |
completed | May 3, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.