Triple
T27681406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Offchurch (associated royal estate) |
E697917
|
entity |
| Predicate | hasModernSettlementName |
P117013
|
FINISHED |
| Object | Offchurch |
—
|
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: Offchurch | Statement: [Offchurch (associated royal estate), hasModernSettlementName, Offchurch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernSettlementName Context triple: [Offchurch (associated royal estate), hasModernSettlementName, Offchurch]
-
A.
hasModernName
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
-
B.
modernNameOfServedSettlement
chosen
Indicates that the object is the current, modern name of the settlement that is or was served by the subject (e.g., a facility, infrastructure, or service).
-
C.
hasModernNamesake
Indicates that an entity is the namesake or inspiration for a modern entity that shares or derives its name from it.
-
D.
hasModernHistoriographicalName
Indicates that an entity is associated with the name or label used for it in modern historiography.
-
E.
hasModernNameLanguage
Indicates that the modern name of an entity is expressed in a particular language.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 27, 2026, 2:47 p.m.