Triple
T35985281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Backlash |
E1040691
|
entity |
| Predicate | hasStipulation |
P113854
|
FINISHED |
| Object | no disqualification matches |
—
|
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: no disqualification matches | Statement: [Backlash, hasStipulation, no disqualification matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStipulation Context triple: [Backlash, hasStipulation, no disqualification matches]
-
A.
hasStipules
Indicates that one entity (typically a plant) possesses stipules as part of its structure.
-
B.
notableStipulation
chosen
Indicates that there is a significant condition, requirement, or clause that meaningfully qualifies or constrains the related entity or relationship.
-
C.
signatureStipulation
Indicates that a condition, requirement, or constraint is formally specified as part of a function, method, or contract signature.
-
D.
hasMatchStipulationHistory
Indicates that there exists a record of conditions, rules, or special terms that have governed one or more matches associated with the subject over time.
-
E.
stipulatedExchange
Indicates a relationship where two or more parties agree in advance to exchange specific goods, services, or values under defined terms or conditions.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a002249ee388190a9501ee7630dc658 |
completed | May 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_6a002189273881909b6b687e2d61f5b1 |
completed | May 10, 2026, 6:11 a.m. |
Created at: May 3, 2026, 4:07 p.m.