Triple
T11159439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oakes test |
E263994
|
entity |
| Predicate | burdenOfProofOn |
P98162
|
FINISHED |
| Object | government |
—
|
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: government | Statement: [Oakes test, burdenOfProofOn, government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burdenOfProofOn Context triple: [Oakes test, burdenOfProofOn, government]
-
A.
standardOfProof
Indicates the level or degree of certainty required to establish that a claim or allegation is true in a given context.
-
B.
stanceOnProofs
Indicates the position or attitude an entity holds regarding the use, value, or nature of proofs.
-
C.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
D.
burdenFound
Indicates that a responsibility, obligation, or load has been identified as existing or resting upon a particular entity.
-
E.
requiresProofOf
Indicates that one entity must provide formal evidence or documentation to validate or authorize another entity.
- F. None of above. chosen
Provenance (4 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8817a90819087820d5241c58851 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cec26fc8190a5497d186306f935 |
completed | April 9, 2026, 8:01 a.m. |
| PDg | Predicate description generation | batch_69d7706116248190a87440bec3960884 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:28 p.m.