Triple
T262800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lynn Woods Reservation |
E5572
|
entity |
| Predicate | hasHistoricUse |
P2417
|
FINISHED |
| Object | water supply watershed |
—
|
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: water supply watershed | Statement: [Lynn Woods Reservation, hasHistoricUse, water supply watershed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricUse Context triple: [Lynn Woods Reservation, hasHistoricUse, water supply watershed]
-
A.
historicallyUsedFor
chosen
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
B.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
C.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
D.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
E.
hasHistoricalPrecursor
Indicates that one entity existed earlier and served as a predecessor, model, or influential forerunner to the other in a historical context.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25d8c7f448190af9145256f994177 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6e07748190834022a65ba6d803 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.