Triple
T20912124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Main |
E514973
|
entity |
| Predicate | hasHydronymColor |
P13022
|
FINISHED |
| Object | red |
—
|
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: red | Statement: [Red Main, hasHydronymColor, red]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHydronymColor Context triple: [Red Main, hasHydronymColor, red]
-
A.
hydronymOf
Indicates that one term is the name of a body of water associated with another geographic entity (e.g., a river, lake, or sea named after a place or feature).
-
B.
hasHydronymOrigin
Indicates that something derives its name from a body of water or hydrological feature.
-
C.
hydronymType
Indicates the specific type or category of a water-related geographical name (e.g., river, lake, sea) associated with a hydronym.
-
D.
hasWaterColor
chosen
Indicates that an entity possesses or is characterized by a particular color of water.
-
E.
watershedName
Indicates the name assigned to the watershed with which an entity is associated.
- 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_69e0b4f9d5ec8190bb2bd27350ed341c |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6ec5f5bc48190a8e7e6af60b158fb |
completed | April 21, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:48 p.m.