Triple
T14943427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Fleet (culverted) |
E372587
|
entity |
| Predicate | culvertedSinceCentury |
P116772
|
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 (culverted), culvertedSinceCentury, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culvertedSinceCentury Context triple: [River Fleet (culverted), culvertedSinceCentury, 18th century]
-
A.
hasAqueduct
Indicates that one entity possesses, contains, or is equipped with an aqueduct that serves or passes through it.
-
B.
numberOfAqueducts
Indicates the quantity of aqueducts associated with or present in a given entity or context.
-
C.
oneOfEarliestMajorAqueductsOf
Indicates that the subject is among the earliest major aqueducts associated with the object.
-
D.
drainageTunnelConstructedIn
Indicates that a drainage tunnel was built or established within a specific location or administrative area.
-
E.
observedSinceCentury
Indicates that one entity has been observed or documented as existing or occurring since a specified century.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded68c1df0819084c0cd61b207d398 |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:38 a.m.