Triple
T3458689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Estonian |
E72967
|
entity |
| Predicate | timeStartApprox |
P48368
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Middle Estonian, timeStartApprox, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeStartApprox Context triple: [Middle Estonian, timeStartApprox, 16th century]
-
A.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
B.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
C.
runsApproximately
Indicates that an entity performs a running action in a manner that is close to, but not exactly matching, a specified time, distance, speed, or other running-related measure.
-
D.
timeOfInitiation
Indicates the specific point in time at which an action, event, or process begins.
-
E.
startTimeAsRepresentative
Indicates the time at which an entity begins serving or acting in a representative capacity.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbae4c18881908b48d16e46f78209 |
completed | March 8, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69adae041d588190a84a02bca94adec8 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:16 p.m.