Triple
T32152412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio v. Roberts |
E821193
|
entity |
| Predicate | timeframeOfInfluence |
P153827
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Ohio v. Roberts, timeframeOfInfluence, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeframeOfInfluence Context triple: [Ohio v. Roberts, timeframeOfInfluence, 1980s]
-
A.
timePeriodInfluence
chosen
Indicates that one time period has an influence or shaping effect on another time period or on events occurring within it.
-
B.
timeframeOfUse
Indicates the period or duration during which something is intended, allowed, or expected to be used.
-
C.
timeHorizonOfImpact
Indicates the span of time over which an action, event, or factor is expected to produce its effects or consequences.
-
D.
lifetimeAffectedBy
Indicates that the duration or span of existence of one entity is influenced, altered, or determined by another entity or factor.
-
E.
hasInfluenceScope
Indicates the range or extent within which an entity’s influence, impact, or authority is effective or applicable.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9eccab88190a2895cbb0332c5a7 |
completed | May 3, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:31 a.m.