Triple
T14406967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Court Run |
E357223
|
entity |
| Predicate | timedBy |
P1936
|
FINISHED |
| Object | Trinity College 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: Trinity College clock | Statement: [Great Court Run, timedBy, Trinity College clock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timedBy Context triple: [Great Court Run, timedBy, Trinity College clock]
-
A.
timeLimited
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
-
B.
time
chosen
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
C.
delayedBy
Indicates that one event, process, or action occurs later than expected or planned due to the influence or interference of another factor or entity.
-
D.
timeBehind
Indicates that one entity occurs or is positioned later in time than another, lagging behind it on a temporal scale.
-
E.
timeAfterAble
Indicates that one event, state, or action occurs after another point in time at which it becomes possible or permissible.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de908804048190a4fe58afc2e0a5b6 |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa1b57881909a033eac8545c417 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:17 a.m.