Triple
T31943699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V_cs |
E815590
|
entity |
| Predicate | suppressesRelativeTo |
P91075
|
FINISHED |
| Object | V_cd in c→d transitions |
—
|
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: V_cd in c→d transitions | Statement: [V_cs, suppressesRelativeTo, V_cd in c→d transitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suppressesRelativeTo Context triple: [V_cs, suppressesRelativeTo, V_cd in c→d transitions]
-
A.
seeksToSuppress
Indicates an entity’s intention or effort to prevent, restrain, or reduce the expression, occurrence, or impact of another entity or activity.
-
B.
suppressedIn
chosen
Indicates that one entity’s presence, activity, or expression is reduced, inhibited, or prevented by another entity or condition.
-
C.
isRelatively
Indicates that one entity is being described, measured, or evaluated in relation to another entity or reference point, rather than in absolute terms.
-
D.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to another entity.
-
E.
suppressedAsPartOf
Indicates that one entity is intentionally prevented, hidden, or constrained as a component or subset of a broader suppression involving another entity.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2758cec8190b0521eb7f2eccb42 |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:06 a.m.