Triple
T32981948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curieuse Island |
E843823
|
entity |
| Predicate | leperColonyEstablished |
P78995
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Curieuse Island, leperColonyEstablished, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leperColonyEstablished Context triple: [Curieuse Island, leperColonyEstablished, early 19th century]
-
A.
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.
-
B.
leperColonyFrom
Indicates that a leper colony originates from, is derived from, or is established based on the referenced source entity.
-
C.
startOfLeprosySettlement
chosen
Indicates the point in time or event when a leprosy settlement is first established or begins to exist.
-
D.
colonyFounded
Indicates that an entity established or created a colony at a particular time or place.
-
E.
regionOfColonyFounded
Indicates the geographic region in which a particular colony was originally founded.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1dc8a108190a994bd39350129fe |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:22 a.m.