Triple
T30069729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combe Martin |
E764144
|
entity |
| Predicate | hasBayNameOrigin |
P64557
|
FINISHED |
| Object | named after the valley of Combe Martin |
—
|
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: named after the valley of Combe Martin | Statement: [Combe Martin, hasBayNameOrigin, named after the valley of Combe Martin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBayNameOrigin Context triple: [Combe Martin, hasBayNameOrigin, named after the valley of Combe Martin]
-
A.
hasBayNameEtymology
chosen
Indicates that the name of an entity is etymologically derived from, or named after, a particular bay.
-
B.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
C.
bayName
Indicates that an entity has the specified name of a bay or is identified by that bay name.
-
D.
hasOriginToponym
Indicates that something originates from, or is derived from, the place denoted by a specific toponym (geographical name).
-
E.
hasNameOriginType
Indicates that there is a specific type or category describing the origin of an entity’s name.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 29, 2026, 7 p.m.