Triple
T5568250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Arthur Historic Site |
E145932
|
entity |
| Predicate | openedAsPenalSettlement |
P6141
|
FINISHED |
| Object | 1830 |
—
|
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: 1830 | Statement: [Port Arthur Historic Site, openedAsPenalSettlement, 1830]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsPenalSettlement Context triple: [Port Arthur Historic Site, openedAsPenalSettlement, 1830]
-
A.
settledAs
Indicates that one entity has been resolved, finalized, or agreed upon in the form or status of another entity.
-
B.
settlementWith
Indicates a relationship where one party reaches or maintains a settlement or agreement with another party, typically resolving a dispute or claim.
-
C.
isSettlementOf
Indicates that one entity is a settlement (such as a town, village, or city) that belongs to, is located within, or is administratively part of another entity.
-
D.
openedAs
chosen
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
E.
possibleSettlementAt
Indicates that a settlement could potentially be established or located at a given place or site.
- 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0203789688190a0bab723186214ad |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b12826c8190969a584d0f53aa44 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.