Triple
T23809046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Hills |
E589794
|
entity |
| Predicate | electorateCode |
P153636
|
FINISHED |
| Object | Port Hills |
—
|
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: Port Hills | Statement: [Port Hills, electorateCode, Port Hills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electorateCode Context triple: [Port Hills, electorateCode, Port Hills]
-
A.
electorateNumber
Indicates the numerical identifier assigned to a specific electorate or voting district within an electoral system.
-
B.
electorateState
Indicates the state or region in which a given electorate (voting district or constituency) is located or to which it belongs.
-
C.
electorate
Indicates that an entity functions as the body of people entitled to vote in relation to a particular political unit, office, or decision.
-
D.
electorateCategory
Indicates the classification of an electorate or voter group into a specific category based on defined electoral or demographic criteria.
-
E.
electorateFrom
Indicates that an electorate or voting body originates from, is drawn from, or is associated with a particular geographic area, jurisdiction, or population source.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c753c46081908b3c9e5c2517b051 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:56 p.m.