Triple
T30460189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tin Can Island |
E774982
|
entity |
| Predicate | postalHistoryCategory |
P164392
|
FINISHED |
| Object | maritime mail |
—
|
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: maritime mail | Statement: [Tin Can Island, postalHistoryCategory, maritime mail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalHistoryCategory Context triple: [Tin Can Island, postalHistoryCategory, maritime mail]
-
A.
postalServiceTradition
Indicates a customary or historically established way in which postal services are organized, operated, or practiced between entities.
-
B.
postalTheme
chosen
Indicates that something is related to, characterized by, or themed around postal services, mail, or mailing systems.
-
C.
categoryHistory
Indicates a relationship where an entity’s past or previous category assignments are recorded or referenced over time.
-
D.
historicalCategory
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
E.
postNominalCategory
Indicates a classification or type assigned to an entity that is expressed in a post-nominal position (after the name or noun).
- 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_69f22494fb60819095d893de0284f886 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686f01dc88190a6ca46fc5c80a486 |
completed | May 2, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:10 p.m.