Triple
T15386292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fontaine |
E367923
|
entity |
| Predicate | uncovers |
P25434
|
FINISHED |
| Object | government conspiracy |
—
|
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 conspiracy | Statement: [Fontaine, uncovers, government conspiracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uncovers Context triple: [Fontaine, uncovers, government conspiracy]
-
A.
covered
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
-
B.
exposes
chosen
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
C.
discloses
Indicates that one entity reveals, makes known, or provides previously non-public information to another entity or to the public.
-
D.
wasUncoveredBy
Indicates that something previously hidden, unknown, or concealed became revealed or discovered through the actions or efforts of a particular agent or process.
-
E.
discovery
Indicates the event or process by which one entity finds, uncovers, or identifies something previously unknown or unrecognized.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e74ff70819094c1a85f51d6e228 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.