Triple
T35680684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquess of Exeter |
E1030999
|
entity |
| Predicate | hasConnectionToCity |
P25162
|
FINISHED |
| Object | Exeter |
E122858
|
NE 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: Exeter | Statement: [Marquess of Exeter, hasConnectionToCity, Exeter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectionToCity Context triple: [Marquess of Exeter, hasConnectionToCity, Exeter]
-
A.
connectsToCityBy
Indicates that one entity is linked or has a direct connection to a specific city, such as through infrastructure, routes, or established relations.
-
B.
hasMetropolitanConnectionWith
Indicates that there is a significant relationship or linkage between two entities based on shared or interacting metropolitan areas, such as through infrastructure, services, or regional integration.
-
C.
hasAssociatedCity
chosen
Indicates that one entity is linked or related to a specific city, typically as its location, base, or primary area of association.
-
D.
hasTargetCity
Indicates that something is directed toward, intended for, or specifically associated with a particular city as its target.
-
E.
hasCityPair
Indicates a relationship that links two cities considered as a connected or associated pair, often for purposes such as travel, trade, or comparison.
- F. None of above.
Provenance (4 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387d06747881908be93c1b2c4f7631 |
completed | June 22, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.