Triple
T4593719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kisimul Castle |
E103557
|
entity |
| Predicate | leaseTerm |
P46529
|
FINISHED |
| Object | 1000 years |
—
|
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: 1000 years | Statement: [Kisimul Castle, leaseTerm, 1000 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaseTerm Context triple: [Kisimul Castle, leaseTerm, 1000 years]
-
A.
leasePeriod
chosen
Indicates the duration or time span for which a lease agreement is valid between parties.
-
B.
leaseAgreement
Indicates a contractual relationship in which one party grants another the right to use an asset or property for a specified period in exchange for agreed payments or conditions.
-
C.
ownershipPeriod
Indicates the span of time during which an entity holds ownership rights over another entity.
-
D.
renewalTerm
Indicates the length or conditions of time for which an agreement, contract, or subscription is extended beyond its initial term.
-
E.
leaseContext
Indicates the contextual circumstances, terms, or conditions under which a lease agreement or leasing relationship exists or is interpreted.
- 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_69bd43dccaf08190aa89e9991a289719 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd593cf8508190acfc6ddb5716e80a |
completed | March 20, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:11 p.m.