Triple
T32153690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James E. Ferguson II |
E821223
|
entity |
| Predicate | partnerInLitigationWith |
P109617
|
FINISHED |
| Object | Julius L. Chambers |
—
|
NE NERFINISHED |
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: Julius L. Chambers | Statement: [James E. Ferguson II, partnerInLitigationWith, Julius L. Chambers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInLitigationWith Context triple: [James E. Ferguson II, partnerInLitigationWith, Julius L. Chambers]
-
A.
legalStrugglePartner
chosen
Indicates that two entities are engaged together as opposing or allied parties in a legal conflict or dispute.
-
B.
lawPartnerOf
Indicates a professional relationship in which two individuals are partners in the same law firm or legal practice.
-
C.
judicialPartner
Indicates a formal partnership or collaborative relationship between entities within a judicial or court-related context.
-
D.
partyToCase
Indicates that an entity is involved in a legal case as one of its formal participants (e.g., plaintiff, defendant, or other party).
-
E.
partnerInConflictResolutionWith
Indicates that two entities collaborate as partners in resolving a specific conflict or dispute.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 12:32 a.m.