Triple
T28658233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tensed Theory of Time |
E725390
|
entity |
| Predicate | opposesClaim |
P74534
|
FINISHED |
| Object | all times are equally real |
—
|
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: all times are equally real | Statement: [The Tensed Theory of Time, opposesClaim, all times are equally real]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposesClaim Context triple: [The Tensed Theory of Time, opposesClaim, all times are equally real]
-
A.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
dissentClaimed
Indicates that an entity has expressed disagreement or opposition to a claim made by another entity.
-
C.
canOppose
Indicates that one entity has the ability or capacity to resist, counteract, or act in opposition to another entity or its actions.
-
D.
opposedOnGroundsOf
Indicates that one party is against or rejects another party, proposal, or action specifically for the stated reasons or justification.
-
E.
opposesLabel
chosen
Indicates that one entity expresses disagreement with, resistance to, or active opposition against another entity or its position.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 28, 2026, 4:56 a.m.