Triple
T30602036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Island |
E778933
|
entity |
| Predicate | hasHumanSettlementSince |
P16159
|
FINISHED |
| Object | 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: 19th century | Statement: [Charles Island, hasHumanSettlementSince, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHumanSettlementSince Context triple: [Charles Island, hasHumanSettlementSince, 19th century]
-
A.
hasHumanSettlement
chosen
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
B.
hasFormerSettlement
Indicates that a location previously contained a settlement that no longer exists or is no longer inhabited.
-
C.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
D.
isOneOfOlderSettlementsIn
Indicates that an entity is among the earlier or historically older settlements located within a specified area or region.
-
E.
hasHumanSettlementDependency
Indicates that one human settlement relies on or is dependent upon another settlement for certain functions, resources, or services.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:25 p.m.