Triple
T24378455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-American Canal |
E614541
|
entity |
| Predicate | unlinedSections |
P155980
|
FINISHED |
| Object | earthen |
—
|
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: earthen | Statement: [All-American Canal, unlinedSections, earthen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unlinedSections Context triple: [All-American Canal, unlinedSections, earthen]
-
A.
line1Section
Indicates that one entity is a specific section or segment of another entity referred to as "line1."
-
B.
hasTreeLinedSections
Indicates that portions of an entity (such as a route, street, or path) are bordered or lined with trees along their length.
-
C.
disputedSections
Indicates that specific parts or portions of something are contested, challenged, or not mutually agreed upon between parties.
-
D.
coveredSectionsLocation
Indicates the specific location or area where the covered sections are situated or applied.
-
E.
hasUnmarkedSections
Indicates that certain sections within an entity lack required labels, annotations, or markings.
- F. None of above. chosen
Provenance (4 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d96e7c8190b2f33a8fd12c32c6 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:02 a.m.