Triple
T6767704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phillips Nizer LLP |
E154764
|
entity |
| Predicate | representedRoleOfClient |
P16985
|
FINISHED |
| Object | attorney |
—
|
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: attorney | Statement: [Phillips Nizer LLP, representedRoleOfClient, attorney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedRoleOfClient Context triple: [Phillips Nizer LLP, representedRoleOfClient, attorney]
-
A.
appointedOnBehalfOf
Indicates that an appointment or designation is made by one party acting in representation of, or for the benefit of, another party.
-
B.
representedFor
Indicates that one entity has acted or served as the official representative or proxy on behalf of another entity.
-
C.
builtOnBehalfOf
Indicates that something was constructed or created by one party acting as a representative or agent for another party.
-
D.
hasCoRepresentativeRole
Indicates that an entity shares or holds a co-representative role or position alongside another entity within the same representational context.
-
E.
legalCaseRole
chosen
Indicates the specific role or capacity an entity holds within a legal case, such as plaintiff, defendant, judge, or attorney.
- 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_69c688109c1c8190added9a221292af0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d231b79c81908a4f7fa8f253706d |
completed | March 27, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:12 p.m.