Triple
T116183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Dividing Range |
E2342
|
entity |
| Predicate | majorRoleIn |
P3512
|
FINISHED |
| Object | Australian river systems |
—
|
LITERAL 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: Australian river systems | Statement: [Great Dividing Range, majorRoleIn, Australian river systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRoleIn Context triple: [Great Dividing Range, majorRoleIn, Australian river systems]
-
A.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
B.
playedKeyRoleIn
chosen
Indicates that an entity had a major, influential, or decisive impact on the occurrence, outcome, or success of another entity or event.
-
C.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
D.
sponsorOccupation
Indicates that one entity serves as the occupation or professional role of a sponsor associated with another entity.
-
E.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a257845c548190bfb49409988d1c57 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a256456d908190b52c937fe6c4343f |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.