Triple
T2234900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kwang-Chou-Wan |
E49256
|
entity |
| Predicate | leaseStart |
P20544
|
FINISHED |
| Object | 1898 |
—
|
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: 1898 | Statement: [Kwang-Chou-Wan, leaseStart, 1898]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaseStart Context triple: [Kwang-Chou-Wan, leaseStart, 1898]
-
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.
leaseOrigin
Indicates that one entity is the original source or starting point from which a lease agreement or leasing arrangement is derived.
-
C.
wasLeasedFor
Indicates that one entity was leased in exchange for a specified payment amount, purpose, or consideration.
-
D.
leaseRecipient
Indicates the party that receives or holds rights to use a property or asset under a lease agreement from another party.
-
E.
tenantsStart
chosen
Indicates that a tenancy relationship begins or is initiated at a specific time or event.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc09297a481909e8fe6ec645de616 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.