Triple
T28647169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birtsmorton |
E725090
|
entity |
| Predicate | hasMoatedSite |
P1098
|
FINISHED |
| Object | Birtsmorton Court |
—
|
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: Birtsmorton Court | Statement: [Birtsmorton, hasMoatedSite, Birtsmorton Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMoatedSite Context triple: [Birtsmorton, hasMoatedSite, Birtsmorton Court]
-
A.
hasMoat
Indicates that one entity is surrounded or protected by a moat associated with another entity.
-
B.
hasArchitecturalSite
Indicates that an entity possesses, contains, or is associated with a specific architectural site.
-
C.
hasArchaeologicalSiteIn
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
-
D.
hasHistoricSite
chosen
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
-
E.
hasArchaeologicalMound
Indicates that an entity possesses or contains an archaeological mound, i.e., a raised earthwork or mound of archaeological significance located on or within it.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 28, 2026, 4:49 a.m.