Triple
T12648604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arroyo |
E302095
|
entity |
| Predicate | derivedFromTopographicalFeature |
P66959
|
FINISHED |
| Object | stream |
—
|
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: stream | Statement: [Arroyo, derivedFromTopographicalFeature, stream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivedFromTopographicalFeature Context triple: [Arroyo, derivedFromTopographicalFeature, stream]
-
A.
topographyBasedOn
Indicates that the topographical characteristics of one entity are derived from, determined by, or modeled using the topography of another entity.
-
B.
topographicalCategory
Indicates the type of landform or surface feature that characterizes the physical terrain associated with an entity.
-
C.
hasLandformOrigin
chosen
Indicates that something originates from, or is formed by, a particular landform.
-
D.
associatedTopography
Indicates a relationship where one entity is linked or connected to a particular topographical feature or terrain.
-
E.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:17 p.m.