Triple
T31954367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ojo de Liebre Lagoon |
E815863
|
entity |
| Predicate | primaryUseNearby |
P199408
|
FINISHED |
| Object | industrial salt production |
—
|
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: industrial salt production | Statement: [Ojo de Liebre Lagoon, primaryUseNearby, industrial salt production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseNearby Context triple: [Ojo de Liebre Lagoon, primaryUseNearby, industrial salt production]
-
A.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
B.
nearbyTownPurpose
chosen
Indicates that a nearby town serves a particular function or purpose in relation to another place or context.
-
C.
nearbyLocationUsedBy
Indicates that one entity makes use of another entity that is located in close physical proximity.
-
D.
nearbyActivityHub
Indicates that one entity is located close enough to another entity that serves as a central hub or focal point for activities or events.
-
E.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:08 a.m.