Triple
T2996628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coosa River (border area) |
E81084
|
entity |
| Predicate | hasLandscapeRole |
P7342
|
FINISHED |
| Object | natural landscape feature |
—
|
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: natural landscape feature | Statement: [Coosa River (border area), hasLandscapeRole, natural landscape feature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandscapeRole Context triple: [Coosa River (border area), hasLandscapeRole, natural landscape feature]
-
A.
hasLandscapeType
chosen
Indicates that an entity possesses or is characterized by a particular type or category of landscape.
-
B.
hasLandscapeFeatures
Indicates that an entity possesses or includes specific landscape-related characteristics or elements.
-
C.
hasOrientation
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
D.
hasPortrait
Indicates that one entity possesses, displays, or is associated with a portrait depicting another entity.
-
E.
hasCoordinateRole
Indicates that one entity shares an equivalent or parallel role or function with another entity within the same context or structure.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f481688190ae8cd1e057f9dfc7 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.