Triple
T5631693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lochkovian |
E147847
|
entity |
| Predicate | startTime_ma |
P64688
|
FINISHED |
| Object | 419.2 |
—
|
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: 419.2 | Statement: [Lochkovian, startTime_ma, 419.2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTime_ma Context triple: [Lochkovian, startTime_ma, 419.2]
-
A.
startTimeAsRepresentative
Indicates the time at which an entity begins serving or acting in a representative capacity.
-
B.
startTimeAsCardinal
Indicates the specific clock time at which an event or action begins, expressed as a cardinal (numeric) value rather than a textual or formatted time.
-
C.
timeAsManagerStart
Indicates the point in time when an entity first began serving in a managerial role over another entity.
-
D.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
E.
timeStartApprox
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0225e8e848190a9ccd48fc0d74e5c |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:40 p.m.