Triple
T21973223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puʻuloa (Pearl Harbor) |
E542642
|
entity |
| Predicate | leaseAgreementYear |
P117579
|
FINISHED |
| Object | 1887 |
—
|
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: 1887 | Statement: [Puʻuloa (Pearl Harbor), leaseAgreementYear, 1887]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaseAgreementYear Context triple: [Puʻuloa (Pearl Harbor), leaseAgreementYear, 1887]
-
A.
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.
-
B.
agreementYear
chosen
Indicates the calendar year in which an agreement between the related entities was made, signed, or came into effect.
-
C.
leaseBegan
Indicates that a lease agreement between parties started or came into effect at a specific time.
-
D.
leasePeriod
Indicates the duration or time span for which a lease agreement is valid between parties.
-
E.
leaseNumber
Indicates the unique identifying number assigned to a specific lease agreement between parties.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1248668ac81909c74b2be62f69fce |
completed | April 28, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8:02 p.m.