Triple
T17785268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Untitled (Free) 1992 |
E444000
|
entity |
| Predicate | temporalMode |
P29111
|
FINISHED |
| Object | event-based |
—
|
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: event-based | Statement: [Untitled (Free) 1992, temporalMode, event-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalMode Context triple: [Untitled (Free) 1992, temporalMode, event-based]
-
A.
hasTemporalResolution
Indicates that one entity specifies the level of temporal detail or granularity at which another entity’s data, observation, or process is measured or represented.
-
B.
temporal
Indicates a relationship that situates one event, state, or entity in time relative to another (e.g., before, after, or during).
-
C.
temporalAspect
chosen
Indicates the time-related characteristics or phase (such as duration, frequency, or temporal status) associated with an event or relationship.
-
D.
temporality
Indicates the time-related relationship between events or states, such as their order, duration, or simultaneity.
-
E.
temporal scope
Indicates the time period or duration over which a particular relationship, condition, or fact holds true.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48792b1c48190836141cfc6656cdd |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.