Triple
T19713253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingholm Quay |
E473404
|
entity |
| Predicate | historicalPeriodOfPortActivity |
P41682
|
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: [Kingholm Quay, historicalPeriodOfPortActivity, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfPortActivity Context triple: [Kingholm Quay, historicalPeriodOfPortActivity, 18th century]
-
A.
historicalPeriodOfMajorActivity
Indicates the historical period during which an entity carried out its most significant or influential activities.
-
B.
historicalPeriodOfIntenseTrade
chosen
Indicates a time span characterized by unusually high levels of trade activity between parties or regions.
-
C.
servedAsMainSeaportUntil
Indicates that an entity functioned as the primary seaport for another entity up to a specified point in time.
-
D.
historicalPeriodOfArrival
Indicates the historical time period during which an entity arrived at or first appeared in a particular place or context.
-
E.
portDevelopmentBegan
Indicates that the process of developing or constructing a port has started.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6440a0f2c8190803ace7f6b4ed6e9 |
completed | April 20, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.