Triple
T30684195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clifford |
E781138
|
entity |
| Predicate | hasTopographicAssociation |
P87992
|
FINISHED |
| Object | cliff |
—
|
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: cliff | Statement: [Clifford, hasTopographicAssociation, cliff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopographicAssociation Context triple: [Clifford, hasTopographicAssociation, cliff]
-
A.
associatedTopography
chosen
Indicates a relationship where one entity is linked or connected to a particular topographical feature or terrain.
-
B.
hasTopographicContext
Indicates that one entity is related to or characterized by a particular topographic or physical landscape context.
-
C.
hasTopographicEffect
Indicates that one entity causes or contributes to a change or influence on the physical terrain or topography of another entity or area.
-
D.
hasTopographicalRole
Indicates that an entity serves a specific functional or positional role within a topographical or spatial context.
-
E.
hasToponymicAssociation
Indicates a relationship where one entity is associated with, derived from, or named after a particular place or geographic name (toponym).
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 29, 2026, 8:33 p.m.