Triple
T21471863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitzgerald v. Hampton |
E529751
|
entity |
| Predicate | partyRoleOfFitzgerald |
P12885
|
FINISHED |
| Object | plaintiff |
—
|
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: plaintiff | Statement: [Fitzgerald v. Hampton, partyRoleOfFitzgerald, plaintiff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyRoleOfFitzgerald Context triple: [Fitzgerald v. Hampton, partyRoleOfFitzgerald, plaintiff]
-
A.
has part in role
Indicates that an entity participates as a component or constituent specifically in a defined role within a larger whole or process.
-
B.
relationshipToZiegfeldFollies
Indicates a relationship or connection that an entity has to the Ziegfeld Follies, such as participation in, association with, or relevance to that theatrical production.
-
C.
partyRoleOfRoderickJackson
Indicates that the specified party role is held or fulfilled by Roderick Jackson.
-
D.
fiancéePortrayedBy
Indicates that a character’s fiancée is depicted or played by a specific actor or performer.
-
E.
namedPersonRole
chosen
Indicates that a person is identified by name as holding a specific role or position in a given context.
- 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_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. |
Created at: April 16, 2026, 6:19 p.m.