Triple
T13007395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ubirr |
E322322
|
entity |
| Predicate | accessAffectedBy |
P25489
|
FINISHED |
| Object | wet season flooding |
—
|
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: wet season flooding | Statement: [Ubirr, accessAffectedBy, wet season flooding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessAffectedBy Context triple: [Ubirr, accessAffectedBy, wet season flooding]
-
A.
accessDeterminedBy
Indicates that the ability to access a resource is governed or controlled by a specified condition, rule, or authority.
-
B.
areAffectedBy
chosen
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
C.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
-
D.
accessScope
Indicates the extent or boundaries of access that one entity has to another entity or resource.
-
E.
affectedControlOf
Indicates that one entity has influenced, altered, or impacted the degree of control another entity has over something.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e9b27ec8190815c40a05b9ba7d0 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:48 p.m.