Triple
T28639308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gryffindor Quidditch team |
E724874
|
entity |
| Predicate | notableChaser |
P203295
|
FINISHED |
| Object | Angelina Johnson |
—
|
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: Angelina Johnson | Statement: [Gryffindor Quidditch team, notableChaser, Angelina Johnson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableChaser Context triple: [Gryffindor Quidditch team, notableChaser, Angelina Johnson]
-
A.
notableChorus
Indicates that an entity is recognized for having a particularly prominent or distinguished chorus section.
-
B.
notableAce
Indicates that one entity is a particularly distinguished or outstanding example (an “ace”) within the domain or activity associated with the other entity.
-
C.
notableDuo
Indicates that two entities are widely recognized together as a famous or significant pair.
-
D.
notableChannel
Indicates that a channel is recognized as particularly significant, prominent, or noteworthy in some context.
-
E.
notableTorchBearer
Indicates that one entity is recognized as a prominent or distinguished carrier or representative of another entity’s cause, tradition, or legacy.
- 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_6a014f7602988190b8f86cb431a9cf12 |
completed | May 11, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_6a014a70ea748190bd86fb9f218103ba |
completed | May 11, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_6a014f751520819088cf1e697e0668ff |
completed | May 11, 2026, 3:39 a.m. |
Created at: April 28, 2026, 4:43 a.m.