Triple
T18994379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Robarts to endorse bills |
E464768
|
entity |
| Predicate | jeopardizes |
P16824
|
FINISHED |
| Object | Mark Robarts's financial security |
—
|
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: Mark Robarts's financial security | Statement: [Mark Robarts to endorse bills, jeopardizes, Mark Robarts's financial security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jeopardizes Context triple: [Mark Robarts to endorse bills, jeopardizes, Mark Robarts's financial security]
-
A.
endangerment
chosen
Indicates a relationship in which one entity exposes another to potential harm, risk, or danger.
-
B.
inhibits
Indicates that one entity prevents, restrains, or reduces the activity, effect, or occurrence of another entity.
-
C.
inDangerSince
Indicates that an entity has been in a state of danger continuously starting from a specified point in time.
-
D.
negates
Indicates that one entity denies, contradicts, or renders false the assertion, state, or effect expressed by another.
-
E.
threatensDeceptionOf
Indicates that one entity poses or communicates a risk of deceiving or misleading 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d680dd2881908a72e732c6b25477 |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.