Triple
T16089756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dejvická |
E390329
|
entity |
| Predicate | terminusRoleStart |
P73129
|
FINISHED |
| Object | 1978-08-12 |
—
|
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: 1978-08-12 | Statement: [Dejvická, terminusRoleStart, 1978-08-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusRoleStart Context triple: [Dejvická, terminusRoleStart, 1978-08-12]
-
A.
terminusFrom
Indicates that something serves as the endpoint or final destination from which a route, path, or connection originates.
-
B.
terminusRegion
Indicates the region or area where something (such as a route, line, or process) ends or reaches its final point.
-
C.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
D.
managementRoleStart
chosen
Indicates the date or point in time when an entity begins holding a particular management role or position.
-
E.
terminusDescription
Indicates the textual description that characterizes the endpoint or final stop of a route, path, or process.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.