Triple
T35786548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Lucy |
E1034579
|
entity |
| Predicate | linkedTerritoriallyTo |
P21614
|
FINISHED |
| Object | Lucy estates |
—
|
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: Lucy estates | Statement: [Lord Lucy, linkedTerritoriallyTo, Lucy estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedTerritoriallyTo Context triple: [Lord Lucy, linkedTerritoriallyTo, Lucy estates]
-
A.
hasTerritorialAssociation
chosen
Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
-
B.
territoryCorrespondedTo
Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
-
C.
linkedToRegion
Indicates that one entity is associated or connected to a specific geographic or administrative region.
-
D.
territoryUnifiedWith
Indicates that two or more territories have been politically or administratively merged into a single unified territorial entity.
-
E.
hasTerritorialInterestIn
Indicates that an entity claims, seeks, or maintains control, influence, or rights over a specific geographic area or territory.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 3, 2026, 4:06 p.m.