Triple
T9585704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogwarts Great Hall (Harry Potter films) |
E231282
|
entity |
| Predicate | propIncludes |
P11236
|
FINISHED |
| Object | long wooden benches |
—
|
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: long wooden benches | Statement: [Hogwarts Great Hall (Harry Potter films), propIncludes, long wooden benches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propIncludes Context triple: [Hogwarts Great Hall (Harry Potter films), propIncludes, long wooden benches]
-
A.
alsoContains
Indicates that something includes, in addition to its primary contents, another specified element or component.
-
B.
usesProp
Indicates that one entity employs, utilizes, or makes use of a particular property, resource, or object in performing an action or fulfilling a function.
-
C.
includesPackage
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
-
D.
includesElement
chosen
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
E.
propUsed
Indicates that a particular property or attribute is utilized or applied in a given context or situation.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99edc2c08190b67b40f6214d46f1 |
completed | April 1, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:06 p.m.