Triple
T14720875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sykes |
E345808
|
entity |
| Predicate | isDerivedFromTopographicTermMeaning |
P53681
|
FINISHED |
| Object | small stream or gully |
—
|
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: small stream or gully | Statement: [Sykes, isDerivedFromTopographicTermMeaning, small stream or gully]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDerivedFromTopographicTermMeaning Context triple: [Sykes, isDerivedFromTopographicTermMeaning, small stream or gully]
-
A.
hasTopographicalRole
Indicates that an entity serves a specific functional or positional role within a topographical or spatial context.
-
B.
hasToponymicDerivatives
chosen
Indicates that a name or term serves as the source from which related place-based or toponymic names are derived.
-
C.
hasOriginToponym
Indicates that something originates from, or is derived from, the place denoted by a specific toponym (geographical name).
-
D.
hasTopographicContext
Indicates that one entity is related to or characterized by a particular topographic or physical landscape context.
-
E.
hasToponymicQualifier
Indicates that an entity is associated with a specific place-related qualifier (toponym) used to distinguish it from other, similarly named entities.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec25d56fc8190871873ca55d49272 |
completed | April 14, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.