Triple
T15613407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rafael Pérez |
E375353
|
entity |
| Predicate | allegedMisconduct |
P83746
|
FINISHED |
| Object | planting evidence |
—
|
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: planting evidence | Statement: [Rafael Pérez, allegedMisconduct, planting evidence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedMisconduct Context triple: [Rafael Pérez, allegedMisconduct, planting evidence]
-
A.
allegedAction
Indicates that an action is claimed or asserted to have occurred, typically without being proven or confirmed.
-
B.
hasAllegationsOf
chosen
Indicates that one entity is accused or suspected of engaging in certain actions, behaviors, or misconduct, but without implying that these accusations are proven.
-
C.
allegedClause
Indicates that a clause or statement is claimed or asserted to be true, typically without confirmed proof or legal determination.
-
D.
hasAllegedDetail
Indicates that an entity is associated with a detail or piece of information that is claimed or reported but not confirmed as factual.
-
E.
allegedUse
Indicates that something is claimed or suspected to have been used, without confirming that the use actually occurred.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e83407c8190abbcd4b7fab0ff85 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:13 a.m.