Triple
T20211389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogwarts viaduct bridge |
E493493
|
entity |
| Predicate | hasMaterialInFiction |
P120354
|
FINISHED |
| Object | stone |
—
|
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: stone | Statement: [Hogwarts viaduct bridge, hasMaterialInFiction, stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaterialInFiction Context triple: [Hogwarts viaduct bridge, hasMaterialInFiction, stone]
-
A.
materialUsedInFiction
chosen
Indicates that a particular material (such as a substance or resource) is used, featured, or plays a role within a fictional work or narrative.
-
B.
hasPlaceInFiction
Indicates that a fictional work or element is associated with, set in, or takes place within a particular fictional location or setting.
-
C.
fictionalMaterial
Indicates that something is made of, composed of, or incorporates a material that exists only in fiction or imagination.
-
D.
hasFictionComponent
Indicates that something includes, contains, or is composed in part of a fictional element or work.
-
E.
hasFeatureInFiction
Indicates that a fictional work includes or portrays a particular feature, trait, or characteristic.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed5691c8190bf253b1d4ee6e88f |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.