Triple
T24289242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Cathan |
E605765
|
entity |
| Predicate | hasPlaceNameLegacy |
P144466
|
FINISHED |
| Object | Kilchattan Bay |
—
|
NE NERFINISHED |
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: Kilchattan Bay | Statement: [Saint Cathan, hasPlaceNameLegacy, Kilchattan Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaceNameLegacy Context triple: [Saint Cathan, hasPlaceNameLegacy, Kilchattan Bay]
-
A.
hasPlaceNamesIn
Indicates that something contains, references, or is associated with one or more place names within it.
-
B.
hasPlaceNamesakeIn
Indicates that something is named after a particular place or location.
-
C.
hasPlaceNamedAfter
Indicates that one place is named in honor of or derived from the name of another place.
-
D.
hasHeritageName
Indicates that an entity is associated with a specific heritage-related name, typically reflecting cultural, historical, or ancestral identity.
-
E.
legacyToponym
chosen
Indicates that one place name is an older or former name historically used to refer to the same geographic entity as another place 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5908e08190a9f150df924a7160 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.