Triple
T26896622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olaf Presents |
E677913
|
entity |
| Predicate | isInUniverseWith |
P76868
|
FINISHED |
| Object | Frozen |
—
|
NE NERFINISHED |
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: Frozen | Statement: [Olaf Presents, isInUniverseWith, Frozen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInUniverseWith Context triple: [Olaf Presents, isInUniverseWith, Frozen]
-
A.
hasInUniverseLocationRelation
Indicates a relationship where an entity is associated with, or situated at, a specific location within a fictional or defined universe or setting.
-
B.
inUniverseLocationType
Indicates the type or category of location that something occupies within a fictional or defined universe or setting.
-
C.
inUniverseRegion
Indicates that an entity is located within or belongs to a specific universe-defined region or area.
-
D.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
E.
livesInWorldWith
chosen
Indicates that one entity exists or resides within the same world or universe as another entity.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61faa702c81909489a6d40e8ee023 |
completed | May 2, 2026, 4 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:48 a.m.