Triple
T28728404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravenclaw Quidditch team |
E730287
|
entity |
| Predicate | notableSeekerOpponent |
P156489
|
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: [Ravenclaw Quidditch team, notableSeekerOpponent, Harry Potter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSeekerOpponent Context triple: [Ravenclaw Quidditch team, notableSeekerOpponent, Harry Potter]
-
A.
notableRivalOpponent
chosen
Indicates that one entity is a particularly significant or well-known rival or opponent of another entity.
-
B.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
C.
notableCompetitorPairs
Indicates that the two entities form a pair of organizations or individuals that are notably recognized as competitors with each other.
-
D.
battleOpponent
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
E.
keyOpponents
Indicates that the subject has primary or most significant opponents identified by the object.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a017590e01c8190b985bb50cc6cd605 |
completed | May 11, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_6a0175406b348190a5809b5f3497d46f |
completed | May 11, 2026, 6:20 a.m. |
Created at: April 28, 2026, 5:57 a.m.