Triple
T5076267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breich Water |
E114403
|
entity |
| Predicate | hasNearbyLandUseHistory |
P19783
|
FINISHED |
| Object | coal mining |
—
|
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: coal mining | Statement: [Breich Water, hasNearbyLandUseHistory, coal mining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyLandUseHistory Context triple: [Breich Water, hasNearbyLandUseHistory, coal mining]
-
A.
hasNearbyLandUse
chosen
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
B.
hasFormerUseNearby
Indicates that something in the vicinity previously had a particular use or function that is no longer current.
-
C.
nearbyHistoricalServiceFor
Indicates that a historical service or facility is located close to a given reference entity or location.
-
D.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
-
E.
historicalServiceNear
Indicates that a historical service or event occurred in close spatial proximity to a specified location or entity.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74d3b0088190a658864cb120eef4 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.