Triple
T18940314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neglinnaya River |
E463362
|
entity |
| Predicate | tunnelConstructionStart |
P106367
|
FINISHED |
| Object | early 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: early 19th century | Statement: [Neglinnaya River, tunnelConstructionStart, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tunnelConstructionStart Context triple: [Neglinnaya River, tunnelConstructionStart, early 19th century]
-
A.
damConstructionStart
Indicates the point in time when the construction work on a dam begins.
-
B.
startConstruction
Indicates that an entity initiates the process of building or constructing another entity or structure.
-
C.
currentBridgeConstructionStart
Indicates the date or time at which the currently ongoing bridge construction project began.
-
D.
roadTunnelOpeningYear
Indicates the calendar year in which a road tunnel was officially opened for use.
-
E.
startOfConstructionApprox
chosen
Indicates that the construction of something began around an approximate or estimated point in time, rather than on a precisely known date.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3eae9b88190b6031c359090782a |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.