Triple
T36255634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brighton Bullet |
E891927
|
entity |
| Predicate | timedIn |
P4815
|
FINISHED |
| Object | seconds |
—
|
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: seconds | Statement: [Brighton Bullet, timedIn, seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timedIn Context triple: [Brighton Bullet, timedIn, seconds]
-
A.
spentTimeIn
Indicates that an entity has spent a certain amount or period of time in a particular place or context.
-
B.
timeRecorded
Indicates that a specific point or period in time has been captured and stored as associated with an event, action, or state.
-
C.
timeStatus
Indicates the temporal state or condition of an event or entity relative to a reference time (e.g., past, present, future, ongoing, or scheduled).
-
D.
timeLimited
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
-
E.
representsTimeIn
chosen
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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5fd3f8481908b9380f82a2310f0 |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.