Triple
T14980546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wheelus Air Base |
E373561
|
entity |
| Predicate | leaseRenewal |
P42574
|
FINISHED |
| Object | 1954 US-Libya base agreement |
—
|
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: 1954 US-Libya base agreement | Statement: [Wheelus Air Base, leaseRenewal, 1954 US-Libya base agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaseRenewal Context triple: [Wheelus Air Base, leaseRenewal, 1954 US-Libya base agreement]
-
A.
renewalTerm
Indicates the length or conditions of time for which an agreement, contract, or subscription is extended beyond its initial term.
-
B.
leaseExtendedUntil
Indicates that an existing lease agreement has been prolonged so that its validity now continues up to a specified end date.
-
C.
officeTermRenewable
Indicates that the term of an office or position can be extended or renewed beyond its initial duration.
-
D.
leasePeriod
Indicates the duration or time span for which a lease agreement is valid between parties.
-
E.
renews
chosen
Indicates that one entity extends, refreshes, or restores the validity, duration, or effectiveness of another entity, often continuing a prior agreement, state, or condition.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6fcebf481909f72cab577560d82 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:52 a.m.