Triple
T26848920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Timothy Shelley |
E676000
|
entity |
| Predicate | landOwnedIn |
P32271
|
FINISHED |
| Object | Sussex |
—
|
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: Sussex | Statement: [Sir Timothy Shelley, landOwnedIn, Sussex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landOwnedIn Context triple: [Sir Timothy Shelley, landOwnedIn, Sussex]
-
A.
ownedLandBy
Indicates that one entity possesses legal or recognized ownership rights over a piece or area of land associated with another entity.
-
B.
landholderIn
chosen
Indicates that one entity holds legal or recognized ownership or tenancy rights over land located within the jurisdiction or bounds of another entity.
-
C.
ownsLandFor
Indicates that one entity possesses or holds ownership rights to land for the benefit, use, or purpose of another entity.
-
D.
Land
Indicates that an entity arrives onto and comes to rest on a surface or ground, typically from the air or another elevated position.
-
E.
landPolicy
Indicates a relationship where an authority defines or applies rules governing the ownership, use, management, or distribution of land.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61b90393c819090595eac8e538e05 |
completed | May 2, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:14 a.m.