Triple
T30183793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonja Hood |
E767276
|
entity |
| Predicate | clubPresidedOver |
P127361
|
FINISHED |
| Object | North Melbourne Football Club |
—
|
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: North Melbourne Football Club | Statement: [Sonja Hood, clubPresidedOver, North Melbourne Football Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubPresidedOver Context triple: [Sonja Hood, clubPresidedOver, North Melbourne Football Club]
-
A.
clubPresided
chosen
Indicates that one entity serves as the presiding leader or head of a club associated with another entity.
-
B.
clubPredecessorOf
Indicates that one club existed earlier and was replaced or succeeded by another club in an organizational or historical sequence.
-
C.
club
Indicates that an entity is a member of, affiliated with, or participates in the activities of a particular club or organized group.
-
D.
clubBase
Indicates the location or place that serves as the primary base or home venue for a club.
-
E.
clubPlaysAt
Indicates that a sports club uses a particular venue or stadium as its home or regular playing location.
- 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f43c8388190a0fce4ef4e392274 |
completed | May 2, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:26 p.m.