Triple
T30076494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dropped Cone (Neumarkt, Cologne) |
E764333
|
entity |
| Predicate | approximateCompletionPeriod |
P53319
|
FINISHED |
| Object | late 20th 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: late 20th century | Statement: [Dropped Cone (Neumarkt, Cologne), approximateCompletionPeriod, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateCompletionPeriod Context triple: [Dropped Cone (Neumarkt, Cologne), approximateCompletionPeriod, late 20th century]
-
A.
periodOfCompletion
Indicates the time span or date by which an action, process, or obligation is completed.
-
B.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
C.
typicalCompletionTimeInWeeks
Indicates the usual number of weeks it takes to complete the associated task, process, or activity.
-
D.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
E.
approximateCompletionEra
chosen
Indicates the general historical period or time range during which something was completed, without specifying an exact 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: April 29, 2026, 7:02 p.m.