Triple
T1994121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boconnoc estate |
E43318
|
entity |
| Predicate | earlierHouseOnSite |
P4380
|
FINISHED |
| Object | medieval manor |
—
|
LITERAL 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: medieval manor | Statement: [Boconnoc estate, earlierHouseOnSite, medieval manor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierHouseOnSite Context triple: [Boconnoc estate, earlierHouseOnSite, medieval manor]
-
A.
houseFounded
Indicates that an entity (such as a house, organization, or lineage) was established or created by another entity or at a specific time.
-
B.
formerSiteOf
chosen
Indicates that a location previously hosted or contained something (such as a structure, organization, or event) that is no longer present there.
-
C.
houseLocatedIn
Indicates that a house is situated within or belongs to a specific geographic location or area.
-
D.
formerHabitat
Indicates that a location once served as a habitat for an entity but no longer does.
-
E.
hasHouse
Indicates that one entity possesses, owns, or is provided with a house in relation to another entity.
- 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8ee02dc81908fec9fd8df7a4f40 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb79ad6888190be99943a9c73cf3e |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.