Triple
T15044641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corpus Clock |
E379191
|
entity |
| Predicate | chronophageMeaning |
P116518
|
FINISHED |
| Object | "time eater" in Greek-derived neologism |
—
|
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 eater" in Greek-derived neologism | Statement: [Corpus Clock, chronophageMeaning, "time eater" in Greek-derived neologism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronophageMeaning Context triple: [Corpus Clock, chronophageMeaning, "time eater" in Greek-derived neologism]
-
A.
swallowed
Indicates that one entity caused another entity to pass from the mouth into the body, typically down the throat.
-
B.
largelyConsumedBy
Indicates that something is mostly or predominantly eaten or used up by a particular consumer or group.
-
C.
eatenAs
Indicates that one entity is consumed or used as food by another entity.
-
D.
eatenAndResurrectedIn
Indicates that an entity was eaten in a particular place or context and later brought back to life or restored there.
-
E.
eatenInStages
Indicates that the act of eating an item occurs over multiple distinct phases or time intervals rather than in a single continuous event.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded830c3c08190a87b81abbbb75377 |
completed | April 15, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 3 a.m.