Triple
T5606418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One O’Clock Gun |
E147243
|
entity |
| Predicate | timeSignallingFunction |
P54969
|
FINISHED |
| Object | marks 1:00 pm each day |
—
|
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: marks 1:00 pm each day | Statement: [One O’Clock Gun, timeSignallingFunction, marks 1:00 pm each day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSignallingFunction Context triple: [One O’Clock Gun, timeSignallingFunction, marks 1:00 pm each day]
-
A.
timeSignalService
chosen
Indicates that one entity provides or is associated with a service that broadcasts or delivers time signals to others.
-
B.
timingMethod
Indicates the method or technique used to measure or record the timing of an event or process.
-
C.
timingStandard
Indicates that one entity specifies or conforms to the timing rules, constraints, or reference schedule defined by another entity.
-
D.
timeSampling
Indicates that one entity specifies how or at what intervals another entity is sampled or measured over time.
-
E.
timeScaleType
Indicates the type or category of temporal scaling applied to an event, process, or measurement (e.g., real-time, accelerated, aggregated).
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020fbb8748190841e5e09db3feef1 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.