Triple
T20223703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salazar Slytherin |
E495321
|
entity |
| Predicate | houseAdmissionPreference |
P60489
|
FINISHED |
| Object | pure-blood students |
—
|
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: pure-blood students | Statement: [Salazar Slytherin, houseAdmissionPreference, pure-blood students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseAdmissionPreference Context triple: [Salazar Slytherin, houseAdmissionPreference, pure-blood students]
-
A.
statedPreference
chosen
Indicates that one entity has explicitly expressed or declared a preference for another entity or option.
-
B.
accommodationPolicy
Indicates the rules or guidelines that govern how accommodations are provided, used, or managed in a given context.
-
C.
petPolicy
Indicates the rules or conditions governing whether and how pets are allowed in relation to a place, service, or arrangement.
-
D.
accommodationStyle
Indicates the manner or type of lodging or housing arrangement provided or used in a given context.
-
E.
housingPattern
Indicates the typical arrangement or distribution of housing units or residential structures within a given area or context.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd827708190b798a30f4e7d533f |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.