Triple
T1292255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edinburgh Castle |
E27571
|
entity |
| Predicate | OneOClockGunPurpose |
P28335
|
FINISHED |
| Object | time signal for ships in the Firth of Forth |
—
|
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: time signal for ships in the Firth of Forth | Statement: [Edinburgh Castle, OneOClockGunPurpose, time signal for ships in the Firth of Forth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OneOClockGunPurpose Context triple: [Edinburgh Castle, OneOClockGunPurpose, time signal for ships in the Firth of Forth]
-
A.
firstShotsFiredAt
Indicates the location or time at which the initial gunshots or opening fire in an incident occurred.
-
B.
firstShotsFiredBy
Indicates which party or entity initiated a conflict or incident by discharging the first shots.
-
C.
firstShotsFiredOn
Indicates that the referenced event or entity marks the initial occurrence of shots being fired on a specified date, time, or occasion.
-
D.
clockType
Indicates the type or category of a clock associated with an entity (e.g., analog, digital, system clock, etc.).
-
E.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bee64d908190b6a9bb479959d523 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c3b9ebdc819098de4d3288201bc1 |
completed | March 1, 2026, 10:54 p.m. |
Created at: March 1, 2026, 7:51 p.m.