Triple
T37329648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William O’Neal |
E926707
|
entity |
| Predicate | providedInformationAbout |
P198128
|
FINISHED |
| Object | Fred Hampton’s residence |
—
|
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: Fred Hampton’s residence | Statement: [William O’Neal, providedInformationAbout, Fred Hampton’s residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedInformationAbout Context triple: [William O’Neal, providedInformationAbout, Fred Hampton’s residence]
-
A.
providedInformationOn
Indicates that one entity supplied or communicated specific information or details to another entity.
-
B.
providedInformationTo
Indicates that one entity has supplied or communicated information to another entity.
-
C.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
D.
controlsInformationAbout
Indicates that one entity has the authority or ability to manage, restrict, or direct access to information concerning another entity.
-
E.
offersInformationOn
Indicates that one entity provides or makes available information about another entity or topic.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
| PDg | Predicate description generation | batch_69fecb4be24481908bda6197d7fc32f4 |
completed | May 9, 2026, 5:51 a.m. |
Created at: May 3, 2026, 4:16 p.m.