Triple
T30268520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Post Office Bay |
E769720
|
entity |
| Predicate | traditionStartedInCentury |
P20068
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Post Office Bay, traditionStartedInCentury, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionStartedInCentury Context triple: [Post Office Bay, traditionStartedInCentury, 18th century]
-
A.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
-
B.
celebratedSinceCentury
chosen
Indicates that a celebration, commemoration, or observance of something has been taking place continuously since a specified century.
-
C.
introducedInCentury
Indicates the century during which something (such as an idea, technology, practice, or entity) was first introduced or came into use.
-
D.
foundedInCentury
Indicates that an entity was established or came into existence during a specified century.
-
E.
traditionInheritedFrom
Indicates that a tradition has been passed down or derived from an earlier source, group, or culture.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: April 29, 2026, 7:43 p.m.