Triple
T11884218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reeve (The Canterbury Tales) |
E282734
|
entity |
| Predicate | managesPropertyFor |
P102059
|
FINISHED |
| Object | a lord |
—
|
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: a lord | Statement: [Reeve (The Canterbury Tales), managesPropertyFor, a lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesPropertyFor Context triple: [Reeve (The Canterbury Tales), managesPropertyFor, a lord]
-
A.
estateManagementCentre
Indicates a relationship where an entity functions as a central facility or office responsible for coordinating and overseeing the management of an estate or group of properties.
-
B.
ownsPropertyIn
Indicates that one entity possesses legal ownership rights over property located within a specified place or jurisdiction.
-
C.
managementCompany
Indicates that one entity serves as the managing company responsible for overseeing or administering another entity.
-
D.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
-
E.
ownsOrLeases
Indicates that one entity has legal rights to use or control another entity either through ownership or through a lease agreement.
- F. None of above. chosen
Provenance (4 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a02ad4819090faef0e0be732ee |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:44 p.m.