Triple
T22567825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hope |
E557997
|
entity |
| Predicate | hasTemporalOrientation |
P116906
|
FINISHED |
| Object | future |
—
|
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: future | Statement: [Hope, hasTemporalOrientation, future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTemporalOrientation Context triple: [Hope, hasTemporalOrientation, future]
-
A.
hasTemporalRole
Indicates that an entity participates in a role or function that is defined, constrained, or characterized by a specific time or temporal context.
-
B.
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.
-
C.
hasTemporalAttribute
chosen
Indicates that an entity is associated with a specific temporal property or characteristic, such as time, duration, or period.
-
D.
hasTemporalDefinition
Indicates that something is associated with a definition or specification that is constrained or characterized by time.
-
E.
hasTemporalUse
Indicates that something is used, applicable, or valid only during a specific time or temporal interval.
- 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_69e11e5ae4ac8190b1f503457603d969 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15fabb9f081908c33c8e2ddf18047 |
completed | April 29, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:52 p.m.