Triple
T462960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitfield |
E7380
|
entity |
| Predicate | isDerivedFromTopographicFeature |
P2833
|
FINISHED |
| Object | field |
—
|
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: field | Statement: [Whitfield, isDerivedFromTopographicFeature, field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDerivedFromTopographicFeature Context triple: [Whitfield, isDerivedFromTopographicFeature, field]
-
A.
topographicIsolation
Indicates the distance from a geographic feature to the nearest point of equal or greater elevation, expressing how isolated it is from higher terrain.
-
B.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
C.
isToponymic
chosen
Indicates that something is related to or derived from a place name (a toponym).
-
D.
topographicMap
Indicates a mapping relationship where a representation shows the physical terrain features and elevation contours of a geographic area.
-
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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efc09eac8190add4bb5823b53ba7 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2ede8eac081908dffade6a5e7950b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.