Triple
T33519064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flick |
E858450
|
entity |
| Predicate | hasTimeFactor |
P140477
|
FINISHED |
| Object | sudden |
—
|
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: sudden | Statement: [Flick, hasTimeFactor, sudden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeFactor Context triple: [Flick, hasTimeFactor, sudden]
-
A.
hasTimeOptions
Indicates that an entity is associated with one or more selectable time choices or configurations.
-
B.
hasTimeDepth
Indicates that something possesses or spans a measurable extent of time, such as duration, historical depth, or temporal layering.
-
C.
hasTimeComponent
chosen
Indicates that something includes, is associated with, or is characterized by a specific temporal aspect or time-related element.
-
D.
hasTimeIndication
Indicates that something includes, specifies, or is associated with a particular time-related indication (such as a timestamp, time period, or temporal marker).
-
E.
timeAsFlagship
Indicates the period during which an entity served as the primary or leading flagship within a fleet or organization.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 1, 2026, 1:39 a.m.