Triple
T35212628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Granadilla and its land |
E1016727
|
entity |
| Predicate | rightIncludes |
P45186
|
FINISHED |
| Object | collection of rents |
—
|
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: collection of rents | Statement: [Lord of Granadilla and its land, rightIncludes, collection of rents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rightIncludes Context triple: [Lord of Granadilla and its land, rightIncludes, collection of rents]
-
A.
includesRight
Indicates that one entity contains, encompasses, or grants a particular right to another entity.
-
B.
coversRight
Indicates that one entity extends over, protects, or conceals the right side of another entity.
-
C.
endsUpWith
Indicates that, as a result of some process or sequence of events, one entity ultimately comes to possess, receive, or be associated with another entity.
-
D.
incorporatesRight
Indicates that one entity includes, absorbs, or integrates another entity as a component or part within itself.
-
E.
rightsInclude
chosen
Indicates that one set of rights encompasses, contains, or subsumes another set of rights.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.