Triple
T19995587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jellicle cats |
E494183
|
entity |
| Predicate | gathersTime |
P9341
|
FINISHED |
| Object | night |
—
|
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: night | Statement: [Jellicle cats, gathersTime, night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gathersTime Context triple: [Jellicle cats, gathersTime, night]
-
A.
timeScatteredAcross
Indicates that instances or occurrences of something are distributed over multiple, non-contiguous points in time rather than concentrated in a single continuous period.
-
B.
collectionTimespan
chosen
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
C.
dutyTime
Indicates the period during which an entity is officially on duty or expected to perform assigned responsibilities.
-
D.
timeStructure
Indicates that one entity defines, constrains, or organizes the temporal framework or schedule within which another entity exists or operates.
-
E.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe3fb288190a935c334e8a5d54e |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:31 p.m.