Triple
T28639305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gryffindor Quidditch team |
E724874
|
entity |
| Predicate | notableSeeker |
P22
|
FINISHED |
| Object | Harry Potter |
—
|
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: Harry Potter | Statement: [Gryffindor Quidditch team, notableSeeker, Harry Potter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSeeker Context triple: [Gryffindor Quidditch team, notableSeeker, Harry Potter]
-
A.
notableExplorer
Indicates that the subject is recognized for significant achievements or prominence in the field of exploration.
-
B.
notableHub
Indicates that an entity serves as a significant central point or focal location for activities, connections, or influence within a particular context.
-
C.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notableShow
Indicates that a show is especially prominent, distinguished, or significant in some noteworthy way.
-
E.
notableDisplay
Indicates that something is prominently or distinctively presented in a way that draws special attention or recognition.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a0149447e448190b0480943de0691ee |
completed | May 11, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_6a0148e2c39c8190a3ad6ea6be902c04 |
completed | May 11, 2026, 3:11 a.m. |
Created at: April 28, 2026, 4:43 a.m.