Triple
T18018148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Fleet |
E431045
|
entity |
| Predicate | historicalPeriodOfCulverting |
P129434
|
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: [River Fleet, historicalPeriodOfCulverting, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfCulverting Context triple: [River Fleet, historicalPeriodOfCulverting, 18th century]
-
A.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
B.
historicalPeriodOfMajorReclamation
Indicates the historical time period during which a major reclamation activity or project primarily took place.
-
C.
historicalDocumentationPeriod
Indicates the time span during which something is documented or recorded in historical sources.
-
D.
culturalPeriod
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
E.
historicalPeriodOfIntensiveQuarrying
Indicates the time span during which quarrying activities were especially frequent or intensive for a given site or resource.
- F. None of above. chosen
Provenance (4 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9bf85c08190a40cef4c6d7b566a |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:24 a.m.