Triple
T27487283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalawao |
E693772
|
entity |
| Predicate | establishedAsLeprosySettlement |
P78995
|
FINISHED |
| Object | 1860s |
—
|
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: 1860s | Statement: [Kalawao, establishedAsLeprosySettlement, 1860s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsLeprosySettlement Context triple: [Kalawao, establishedAsLeprosySettlement, 1860s]
-
A.
startOfLeprosySettlement
chosen
Indicates the point in time or event when a leprosy settlement is first established or begins to exist.
-
B.
residenceAfterLeprosy
Indicates that an entity’s place of residence after experiencing or being treated for leprosy is the specified location.
-
C.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
D.
leperColonyUntil
Indicates that an entity was confined to or associated with a leper colony up to a specified time or condition, after which this association ceased.
-
E.
statusAfterLeprosy
Indicates the condition or social/legal status an entity has after experiencing or being diagnosed with leprosy.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 27, 2026, 1:03 p.m.