Triple
T5041125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waternish |
E113545
|
entity |
| Predicate | hasTraditionalLandUse |
P43475
|
FINISHED |
| Object | sheep grazing |
—
|
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: sheep grazing | Statement: [Waternish, hasTraditionalLandUse, sheep grazing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalLandUse Context triple: [Waternish, hasTraditionalLandUse, sheep grazing]
-
A.
formerLandUse
Indicates the type of land use that characterized a location prior to its current or present use.
-
B.
hasLandUseCharacter
chosen
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
C.
isTraditionallyOccupiedBy
Indicates that a place, territory, or role has historically and customarily been inhabited or held by a particular group or type of entity.
-
D.
majorLandUse
Indicates the primary way a given area of land is utilized or designated (e.g., residential, commercial, agricultural).
-
E.
hasHistoricalLandCover
Indicates that an entity is associated with information about the land cover that existed in a specified area during a past time period.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73de73008190b89aec9a76b43e4f |
completed | March 20, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.