Triple
T34844527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Line Canal Trail |
E1004428
|
entity |
| Predicate | historicalUseOfCorridor |
P61930
|
FINISHED |
| Object | irrigation for agriculture |
—
|
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: irrigation for agriculture | Statement: [High Line Canal Trail, historicalUseOfCorridor, irrigation for agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalUseOfCorridor Context triple: [High Line Canal Trail, historicalUseOfCorridor, irrigation for agriculture]
-
A.
formerUseOfCorridor
chosen
Indicates that a corridor was previously used for a particular purpose or function, but is no longer used in that way.
-
B.
formerNameOfCorridor
Indicates that one corridor previously had a different name, which is now the current name of another corridor.
-
C.
historicalUseOfArea
Indicates how an area was used or what activities occurred there during a past period.
-
D.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
E.
isOnHistoricTransportCorridor
Indicates that something is located along or within a transportation route that has recognized historical significance.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a008b8938608190adaccbd720111a18 |
completed | May 10, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_6a008b24baac8190baaaf50c2e9cc6bd |
completed | May 10, 2026, 1:41 p.m. |
Created at: May 3, 2026, 4 p.m.