Triple
T27372339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L. B. Sullivan |
E690358
|
entity |
| Predicate | allegedHarm |
P65298
|
FINISHED |
| Object | damage to reputation |
—
|
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: damage to reputation | Statement: [L. B. Sullivan, allegedHarm, damage to reputation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedHarm Context triple: [L. B. Sullivan, allegedHarm, damage to reputation]
-
A.
allegedInjury
chosen
Indicates that an injury is claimed or asserted to have occurred, typically without being legally or factually established.
-
B.
recognizedHarm
Indicates that an entity has identified or acknowledged the existence or occurrence of harm affecting another entity or situation.
-
C.
allegedUse
Indicates that something is claimed or suspected to have been used, without confirming that the use actually occurred.
-
D.
allegedAction
Indicates that an action is claimed or asserted to have occurred, typically without being proven or confirmed.
-
E.
hasAllegationsOf
Indicates that one entity is accused or suspected of engaging in certain actions, behaviors, or misconduct, but without implying that these accusations are proven.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 12:19 p.m.