Triple
T1473670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | qutb |
E27191
|
entity |
| Predicate | temporalAspect |
P29111
|
FINISHED |
| Object | believed to exist in every age |
—
|
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: believed to exist in every age | Statement: [qutb, temporalAspect, believed to exist in every age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalAspect Context triple: [qutb, temporalAspect, believed to exist in every age]
-
A.
temporalRelation
Indicates a relationship that specifies how two events or states are positioned relative to each other in time (e.g., before, after, or overlapping).
-
B.
timePerspective
Indicates how an entity conceptually relates to or orients itself toward time, such as focusing on past, present, or future.
-
C.
hasTenseAspect
Indicates that a verb or clause is associated with a specific grammatical tense and aspect configuration.
-
D.
hasTenseAspectSystem
Indicates that a language or clause employs a particular system for expressing tense and aspect distinctions.
-
E.
tempo
Indicates the speed or pace at which an action, process, or sequence unfolds over time.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c52bbb748190aaa804438d31f4c2 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8:01 p.m.