Triple
T8909388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timeball Tower |
E212141
|
entity |
| Predicate | signallingMethod |
P19148
|
FINISHED |
| Object | dropping time ball at a predetermined time |
—
|
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: dropping time ball at a predetermined time | Statement: [Timeball Tower, signallingMethod, dropping time ball at a predetermined time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signallingMethod Context triple: [Timeball Tower, signallingMethod, dropping time ball at a predetermined time]
-
A.
usesSignaling
Indicates that one entity communicates or coordinates with another by emitting, transmitting, or interpreting signals.
-
B.
signallingSystem
chosen
Indicates that one entity functions as a signalling system used to transmit information or cues to another entity.
-
C.
usesSignallingPractice
Indicates that one entity employs or follows a particular signalling practice in its communication or behavior.
-
D.
appointmentMethod
Indicates how an appointment is arranged, such as the channel, process, or means used to schedule it.
-
E.
signalReach
Indicates the extent or range over which a signal can be effectively transmitted or received between entities.
- 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc65207bbc8190be181555b9564797 |
completed | April 1, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:55 p.m.