Triple
T26527740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Devon (English Courtenay branch) |
E670737
|
entity |
| Predicate | hasEstateRegion |
P87581
|
FINISHED |
| Object | Teignbridge |
—
|
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: Teignbridge | Statement: [Earl of Devon (English Courtenay branch), hasEstateRegion, Teignbridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstateRegion Context triple: [Earl of Devon (English Courtenay branch), hasEstateRegion, Teignbridge]
-
A.
hasAssociatedEstate
Indicates that one entity is linked to, or has responsibility for, a particular estate or property.
-
B.
hasEstateType
Indicates that an entity possesses or is associated with a particular category or type of estate.
-
C.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
D.
landedEstatesRegion
chosen
Indicates that an entity’s landed estates are located within or associated with a particular geographic region.
-
E.
hasProvinceOrRegion
Indicates that one entity includes, is associated with, or is located within a specific province or region as an administrative or geographic subdivision.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 1:33 a.m.