Triple
T14528218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enchanted Forest |
E340833
|
entity |
| Predicate | keyTo |
P98500
|
FINISHED |
| Object | Arendelle’s hidden past |
—
|
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: Arendelle’s hidden past | Statement: [Enchanted Forest, keyTo, Arendelle’s hidden past]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyTo Context triple: [Enchanted Forest, keyTo, Arendelle’s hidden past]
-
A.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
B.
keyOf
Indicates that one entity functions as the key (identifier or access token) associated with another entity.
-
C.
areKeyTo
chosen
Indicates that something is essential or critically important for enabling, achieving, or understanding something else.
-
D.
keyTarget
Indicates that one entity serves as the primary focus, objective, or intended recipient of another entity’s action, function, or influence.
-
E.
keyText
Indicates that a piece of text functions as a key or identifier used to access, reference, or unlock something in a system or 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_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. |
Created at: April 10, 2026, 1:22 a.m.