Triple
T4915900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Famous Blue Raincoat |
E110347
|
entity |
| Predicate | referencesTime |
P11533
|
FINISHED |
| Object | four in the morning |
—
|
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: four in the morning | Statement: [Famous Blue Raincoat, referencesTime, four in the morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referencesTime Context triple: [Famous Blue Raincoat, referencesTime, four in the morning]
-
A.
epochReference
Indicates a temporal relationship where one time expression is interpreted relative to a specified reference epoch or baseline time.
-
B.
associatedWithTime
chosen
Indicates a relationship where something is linked or connected to a specific point or period in time.
-
C.
relatedTimeStandard
Indicates that one time-related entity is defined, interpreted, or aligned according to a particular time standard or reference timescale.
-
D.
linkedToDate
Indicates that an entity is associated or connected to a specific date or point in time.
-
E.
temporalRelation
Indicates a relationship that specifies how two events or states are positioned relative to each other in time (e.g., before, after, or overlapping).
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6fa404f881908b4f983983ac7076 |
completed | March 20, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.