Triple
T3458588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jotunheim |
E72965
|
entity |
| Predicate | associatedWithElement |
P48367
|
FINISHED |
| Object | ice |
—
|
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: ice | Statement: [Jotunheim, associatedWithElement, ice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithElement Context triple: [Jotunheim, associatedWithElement, ice]
-
A.
associatedWithClass
Indicates that an entity has a connection or linkage to a particular class or category, without specifying the exact nature of that relationship.
-
B.
associatedWithMatch
Indicates a relationship where an entity is linked or connected to a particular match or matching event.
-
C.
associatedWithText
Indicates that an entity has a contextual or semantic connection to a specific piece of text.
-
D.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
E.
associatedWithRule
Indicates that an entity is linked or connected to a specific rule, such as being governed, constrained, or defined by that rule.
- F. None of above. chosen
Provenance (4 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbae4c18881908b48d16e46f78209 |
completed | March 8, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69adae041d588190a84a02bca94adec8 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:16 p.m.