Triple
T35624795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harden, New South Wales |
E1029419
|
entity |
| Predicate | oftenCollectivelyKnownAs |
P52939
|
FINISHED |
| Object | Harden-Murrumburrah |
—
|
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: Harden-Murrumburrah | Statement: [Harden, New South Wales, oftenCollectivelyKnownAs, Harden-Murrumburrah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenCollectivelyKnownAs Context triple: [Harden, New South Wales, oftenCollectivelyKnownAs, Harden-Murrumburrah]
-
A.
collectivelyKnownAs
chosen
Indicates that multiple entities are referred to together under a single shared name or designation.
-
B.
collectiveNameForm
Indicates that one entity serves as the collective or group name form used to refer to multiple members of another entity or class.
-
C.
followersKnownAs
Indicates that the followers of an entity are referred to by a particular name or label.
-
D.
knownForCollectionOf
Indicates that one entity is recognized or notable specifically for its collection or assemblage of another type of entity.
-
E.
knownAsOneOf
Indicates that an entity is recognized or referred to as one member of a specified set of alternative names, labels, or identities.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 3, 2026, 4:05 p.m.