Triple
T28639312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gryffindor Quidditch team |
E724874
|
entity |
| Predicate | notableBeater |
P203305
|
FINISHED |
| Object | Fred Weasley |
—
|
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: Fred Weasley | Statement: [Gryffindor Quidditch team, notableBeater, Fred Weasley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBeater Context triple: [Gryffindor Quidditch team, notableBeater, Fred Weasley]
-
A.
hasNotableBeat
Indicates that an entity (such as a journalist or reporter) is professionally assigned to cover a specific topic, area, or subject as their primary reporting focus.
-
B.
beater
Indicates that one entity physically strikes, hits, or beats another entity.
-
C.
notableAce
Indicates that one entity is a particularly distinguished or outstanding example (an “ace”) within the domain or activity associated with the other entity.
-
D.
notableBatter
Indicates that the subject is a batter who is particularly prominent, distinguished, or noteworthy in the context of batting.
-
E.
notableBB
Indicates that one entity is notably associated with another entity in the context of basketball (e.g., as a prominent player, team, event, or achievement).
- 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_6a01531add1c8190b51add7bb046e2cb |
completed | May 11, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_6a014fef3d8c81909b509d51d0c4cdc7 |
completed | May 11, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_6a01531a3a4c8190ac8cb040cc36e96b |
completed | May 11, 2026, 3:55 a.m. |
Created at: April 28, 2026, 4:43 a.m.