Triple
T14528217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enchanted Forest |
E340833
|
entity |
| Predicate | timeOfSealing |
P114622
|
FINISHED |
| Object | after conflict between Arendelle and Northuldra |
—
|
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: after conflict between Arendelle and Northuldra | Statement: [Enchanted Forest, timeOfSealing, after conflict between Arendelle and Northuldra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfSealing Context triple: [Enchanted Forest, timeOfSealing, after conflict between Arendelle and Northuldra]
-
A.
sealedBy
Indicates that one entity is closed, secured, or made airtight/watertight through the action or presence of another entity.
-
B.
isSealed
Indicates that an entity is closed off or secured so that nothing can enter, exit, or be altered.
-
C.
timeOfAttestation
Indicates the specific time at which a statement, document, or claim is formally attested or verified.
-
D.
hasDateOnSeal
Indicates that a seal bears or includes a specific date as part of its inscription or design.
-
E.
securedDate
Indicates the date on which something was formally obtained, locked in, or guaranteed (e.g., a deal, reservation, or right).
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea051bc608190ad4d516c5e7bca43 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb5ac548190932f238e37271741 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:22 a.m.