Triple
T28639306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gryffindor Quidditch team |
E724874
|
entity |
| Predicate | notableKeeper |
P203288
|
FINISHED |
| Object | Oliver Wood |
—
|
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: Oliver Wood | Statement: [Gryffindor Quidditch team, notableKeeper, Oliver Wood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableKeeper Context triple: [Gryffindor Quidditch team, notableKeeper, Oliver Wood]
-
A.
notableHolder
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
-
B.
notableKey
Indicates that the referenced key is of particular importance or prominence compared to other keys in the same context.
-
C.
notableStore
Indicates that a store is recognized as notable or significant in some context (e.g., historically, culturally, or commercially).
-
D.
notableSave
Indicates that an entity is recognized for having made a particularly significant or memorable save (e.g., in a game, match, or critical situation).
-
E.
notableManager
Indicates that an entity has, or is associated with, a manager who is particularly prominent, distinguished, or widely recognized.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a014a0b57dc8190b04ce51156ab95fa |
completed | May 11, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_6a0149afa57c8190a83257085766d916 |
completed | May 11, 2026, 3:14 a.m. |
| PDg | Predicate description generation | batch_6a014a0ab56c819082ce383fb5987654 |
completed | May 11, 2026, 3:16 a.m. |
Created at: April 28, 2026, 4:43 a.m.