Triple
T17766486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neukieritzsch |
E443518
|
entity |
| Predicate | usesTimeNotation |
P2162
|
FINISHED |
| Object | 24-hour clock |
—
|
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: 24-hour clock | Statement: [Neukieritzsch, usesTimeNotation, 24-hour clock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTimeNotation Context triple: [Neukieritzsch, usesTimeNotation, 24-hour clock]
-
A.
timeNotation
chosen
Indicates the specific system or format used to represent and write times (e.g., 12-hour vs 24-hour notation).
-
B.
timeInterpretation
Indicates how a given temporal expression or event should be understood or interpreted in terms of time (e.g., its reference point, scope, or temporal role).
-
C.
timeDescribedAs
Indicates that a specific time or temporal interval is characterized, labeled, or expressed using a particular description or representation.
-
D.
dimensionOfTime
Indicates a temporal measurement or extent that specifies how long something lasts or when it occurs.
-
E.
representsTimeIn
Indicates that one entity expresses, encodes, or specifies the time at which another entity occurs, is valid, or is observed.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485fc03e48190a8044e1b40f66f20 |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:11 a.m.