Triple
T38415577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogwarts Sorting Ceremony (1991) |
E901591
|
entity |
| Predicate | sortsIntoHouse |
P190856
|
FINISHED |
| Object | Gryffindor |
—
|
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: Gryffindor | Statement: [Hogwarts Sorting Ceremony (1991), sortsIntoHouse, Gryffindor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sortsIntoHouse Context triple: [Hogwarts Sorting Ceremony (1991), sortsIntoHouse, Gryffindor]
-
A.
takesIntoHouse
Indicates that one entity brings or leads another entity into a house or dwelling.
-
B.
houseFoundedOrder
Indicates that a house or organization was established or founded according to a particular sequence or order relative to other houses or organizations.
-
C.
house1
Indicates that something is identified or classified as a house or dwelling.
-
D.
house2
Indicates a relationship where one entity is a secondary, related, or alternative house associated with another entity.
-
E.
homeManager
Indicates that one entity manages, oversees, or is responsible for the operations or affairs of another entity’s home or household.
- F. None of above. chosen
Provenance (4 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fcd148e6d4819082c118832ecc599b |
completed | May 7, 2026, 5:52 p.m. |
Created at: May 3, 2026, 4:31 p.m.