Triple
T34980500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rooney crime organization |
E1008798
|
entity |
| Predicate | includesAssociate |
P10953
|
FINISHED |
| Object | Michael Sullivan |
E308441
|
NE 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: Michael Sullivan | Statement: [Rooney crime organization, includesAssociate, Michael Sullivan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesAssociate Context triple: [Rooney crime organization, includesAssociate, Michael Sullivan]
-
A.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
B.
endedAssociationWith
Indicates that a previously existing association or relationship between two entities has been terminated or discontinued.
-
C.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
D.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
E.
hasAssociateMember
chosen
Indicates that an entity has another entity connected to it in a non-full, typically limited or secondary, membership capacity.
- F. None of above.
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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3803ee73348190b377b15cf93ac660 |
completed | June 21, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.