Triple
T21924387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independence Trail |
E541403
|
entity |
| Predicate | originalUseOfDitch |
P44099
|
FINISHED |
| Object | mining water conveyance |
—
|
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: mining water conveyance | Statement: [Independence Trail, originalUseOfDitch, mining water conveyance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalUseOfDitch Context triple: [Independence Trail, originalUseOfDitch, mining water conveyance]
-
A.
excavatedUsing
Indicates that an excavation was carried out with the aid of a specified tool, method, or equipment.
-
B.
reclamationUse
Indicates the use or intended use of something specifically for reclamation, restoration, or recovery purposes.
-
C.
firstHistoricalUse
Indicates that the subject entity represents the earliest known or recorded instance of the object entity being used or occurring in history.
-
D.
formerLandUse
chosen
Indicates the type of land use that characterized a location prior to its current or present use.
-
E.
excavationPurpose
Indicates that an excavation is carried out with a specific intended purpose or objective.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1233dc504819083ee27e253805189 |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:45 p.m.