Triple
T12374629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Bath |
E295089
|
entity |
| Predicate | hasHistoricalEraOfSignificance |
P4928
|
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: [Port of Bath, hasHistoricalEraOfSignificance, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalEraOfSignificance Context triple: [Port of Bath, hasHistoricalEraOfSignificance, 19th century]
-
A.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
-
B.
hasHistoricalSignificance
Indicates that something possesses notable importance or influence within a historical context or period.
-
C.
historicalPeriodOfSignificance
chosen
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
D.
hasStateOfSignificance
Indicates that something possesses a particular condition, status, or level that is considered important or meaningful in a given context.
-
E.
historicalNotability
Indicates that an entity is recognized as having significant importance, influence, or prominence in history.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93fa8ca7c8190b3f8e9c2ec23e837 |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.