Triple
T21471864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitzgerald v. Hampton |
E529751
|
entity |
| Predicate | partyRoleOfHampton |
P144489
|
FINISHED |
| Object | defendant |
—
|
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: defendant | Statement: [Fitzgerald v. Hampton, partyRoleOfHampton, defendant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyRoleOfHampton Context triple: [Fitzgerald v. Hampton, partyRoleOfHampton, defendant]
-
A.
HarrisonRole
Indicates that an entity holds, has held, or is associated with a specific role or position in relation to Harrison.
-
B.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
C.
partySystemRole
Indicates the specific functional role or capacity that a party assumes within a given system or context.
-
D.
hasGovernmentBodyRole
Indicates that an entity holds or is assigned a specific role or position within a governmental body or institution.
-
E.
notableOfficerRole
Indicates that an entity holds or has held a particularly significant or distinguished officer position within an organization or institution.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea14756081908c615590c68904d5 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:19 p.m.