Triple
T27445727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coxs River |
E692272
|
entity |
| Predicate | waterBodyCreatedOn |
P21976
|
FINISHED |
| Object | Lake Burragorang |
—
|
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: Lake Burragorang | Statement: [Coxs River, waterBodyCreatedOn, Lake Burragorang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterBodyCreatedOn Context triple: [Coxs River, waterBodyCreatedOn, Lake Burragorang]
-
A.
waterBodyCreated
chosen
Indicates that one entity is responsible for the formation or creation of a particular body of water.
-
B.
waterBodyCreatedNearby
Indicates that a water body has been formed or established in close spatial proximity to a specified reference location or entity.
-
C.
waterbodyID
Indicates a unique identifier that links an entity to a specific body of water.
-
D.
waterBodyView
Indicates that an entity has a visual outlook or view onto a body of water, such as a lake, river, or ocean.
-
E.
waterbodyUsedFor
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
- 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_69ef5206c9248190b5975c2a7f9d229c |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 12:46 p.m.