Triple
T26944969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dwarfs’ cottage |
E678610
|
entity |
| Predicate | hasDoorSign |
P107436
|
FINISHED |
| Object | “Seven Dwarfs” (various adaptations and merchandise) |
—
|
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: “Seven Dwarfs” (various adaptations and merchandise) | Statement: [dwarfs’ cottage, hasDoorSign, “Seven Dwarfs” (various adaptations and merchandise)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoorSign Context triple: [dwarfs’ cottage, hasDoorSign, “Seven Dwarfs” (various adaptations and merchandise)]
-
A.
hasDoor
Indicates that one entity possesses or is equipped with a door that provides access to or through it.
-
B.
doorSymbol
chosen
Indicates a symbolic representation that denotes or marks the presence or concept of a door.
-
C.
hasDoorGuard
Indicates that an entity has another entity serving as a guard for its door or entrance.
-
D.
hasDoorSide
Indicates that one entity represents a specific side or face of a door in relation to another entity.
-
E.
hasParkServiceSign
Indicates that an entity features or is marked by an official park service sign.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 6:20 a.m.