Triple
T25618436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castlemaine Football Netball Club |
E642224
|
entity |
| Predicate | notableJunior |
P193288
|
FINISHED |
| Object | Dustin Martin |
—
|
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: Dustin Martin | Statement: [Castlemaine Football Netball Club, notableJunior, Dustin Martin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableJunior Context triple: [Castlemaine Football Netball Club, notableJunior, Dustin Martin]
-
A.
notableLevel
Indicates the degree or extent to which something is considered notable or significant.
-
B.
notableOrdinary
Indicates that an entity is notable or significant despite being otherwise ordinary or typical in its category.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notablePupil
Indicates that one person is a distinguished or noteworthy student or protégé of another person.
-
E.
notableSingle
Indicates that the subject is particularly recognized or distinguished for one specific, individual instance (such as a single work, 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
| PDg | Predicate description generation | batch_69fd4128ed908190837ec9936774a1cf |
completed | May 8, 2026, 1:49 a.m. |
Created at: April 21, 2026, 5:02 p.m.