Triple
T3323584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milton, Brisbane |
E69855
|
entity |
| Predicate | stateElectorate |
P11212
|
FINISHED |
| Object | Cooper |
E341256
|
NE FINISHED |
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: Cooper | Statement: [Milton, Brisbane, stateElectorate, Cooper]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cooper Context triple: [Milton, Brisbane, stateElectorate, Cooper]
-
A.
Cooper
Cooper is a common English surname of occupational origin, traditionally referring to a maker or repairer of wooden casks and barrels.
-
B.
Cooper
chosen
Cooper is an electoral district of the Queensland Legislative Assembly that includes suburbs such as Red Hill in Brisbane.
-
C.
Humility Cooper
Humility Cooper was a young passenger on the Mayflower, traveling as a ward of Edward and Ann Tilley among the early English settlers of Plymouth Colony.
-
D.
Lloyd
Lloyd is the middle name of William Lloyd Garrison, the prominent 19th-century American abolitionist and social reformer.
-
E.
Lloyd
Lloyd is a masculine given name of Welsh origin meaning "grey" or "grey-haired."
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ad85a1829881908942c14075644d0d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb13e6c288190805f8abcd3acc906 |
completed | March 8, 2026, 5:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b31a7b26248190b9bf159982d7d19e |
completed | March 12, 2026, 7:56 p.m. |
Created at: March 8, 2026, 3:11 p.m.