Triple
T10036630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baikonur |
E205186
|
entity |
| Predicate | leaseExtendedUntil |
P92048
|
FINISHED |
| Object | 2050 |
—
|
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: 2050 | Statement: [Baikonur, leaseExtendedUntil, 2050]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaseExtendedUntil Context triple: [Baikonur, leaseExtendedUntil, 2050]
-
A.
extensionEffectiveDate
Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
-
B.
leasePeriod
Indicates the duration or time span for which a lease agreement is valid between parties.
-
C.
laterRenewedFor
Indicates that an existing agreement, contract, or arrangement was renewed again at a subsequent, later time.
-
D.
renewalDate
Indicates the date on which an existing agreement, subscription, or arrangement is scheduled to be renewed or extended.
-
E.
renewalTerm
Indicates the length or conditions of time for which an agreement, contract, or subscription is extended beyond its initial term.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce4bb3408190ac5dae4718ef7cad |
completed | April 2, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 8:55 p.m.