Triple
T8746334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingston and Arthur’s Vale Historic Area |
E207836
|
entity |
| Predicate | establishedAsSettlement |
P16153
|
FINISHED |
| Object | 1788 |
—
|
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: 1788 | Statement: [Kingston and Arthur’s Vale Historic Area, establishedAsSettlement, 1788]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsSettlement Context triple: [Kingston and Arthur’s Vale Historic Area, establishedAsSettlement, 1788]
-
A.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
B.
establishedAs
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
C.
establishedTo
Indicates that one entity was created, founded, or set up for the purpose of serving, supporting, or enabling another entity.
-
D.
hasCityStatusSettlement
Indicates that a settlement possesses official recognition or designation as a city.
-
E.
settledInYear
chosen
Indicates the specific calendar year in which an entity became established, inhabited, or formally settled in a particular place or status.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d75e7c88190a9e78fadb979e1b6 |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.