Triple
T20595347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hufflepuff |
E506035
|
entity |
| Predicate | symbolicDirection |
P30236
|
FINISHED |
| Object | down (earth-associated) |
—
|
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: down (earth-associated) | Statement: [Hufflepuff, symbolicDirection, down (earth-associated)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolicDirection Context triple: [Hufflepuff, symbolicDirection, down (earth-associated)]
-
A.
directionalDesignation
chosen
Indicates a relationship where one entity is assigned or labeled with a specific directional orientation relative to another entity or reference frame.
-
B.
definesDirection
Indicates that one entity specifies or establishes the orientation, course, or path along which another entity is directed or proceeds.
-
C.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
D.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
E.
directionalRole
Indicates a role or function defined in terms of a direction or orientation relative to another entity or reference frame.
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1b1c6c8190a2d85e7a390fc6a5 |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.