Triple
T10595402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dominique DiPierro |
E250098
|
entity |
| Predicate | worksOnCase |
P2453
|
FINISHED |
| Object | fsociety investigation |
—
|
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: fsociety investigation | Statement: [Dominique DiPierro, worksOnCase, fsociety investigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksOnCase Context triple: [Dominique DiPierro, worksOnCase, fsociety investigation]
-
A.
worksOnIssue
chosen
Indicates that an entity (typically a person or team) is actively engaged in addressing, resolving, or contributing work toward a specific issue.
-
B.
worksAs
Indicates that an entity performs the role, job, or occupation specified by another entity.
-
C.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
D.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
E.
worksThrough
Indicates that one entity performs an action, causes an effect, or achieves a result by using, employing, or acting via another entity as an intermediary or means.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5278cbf9081909ef419b0144d5019 |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d5190a6dfc819088262957551808a1 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:41 p.m.