Triple
T34980499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rooney crime organization |
E1008798
|
entity |
| Predicate | includesFamilyMember |
P3600
|
FINISHED |
| Object | Connor Rooney |
E308442
|
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: Connor Rooney | Statement: [Rooney crime organization, includesFamilyMember, Connor Rooney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFamilyMember Context triple: [Rooney crime organization, includesFamilyMember, Connor Rooney]
-
A.
immediateFamilyMemberOf
Indicates a close familial relationship where one person is a direct or closely related family member (such as parent, child, sibling, or spouse) of another.
-
B.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
C.
containsFamily
chosen
Indicates that one entity includes or encompasses members of a particular family group within it.
-
D.
coveredFamilyMember
Indicates that one person is included as an eligible dependent or beneficiary under another person’s insurance or benefit coverage.
-
E.
hasHouseholdMember
Indicates that one entity is a member of the same household as another entity.
- 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_6a37c623f9cc81908213ceb2e8be7ef2 |
completed | June 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.