Triple
T758415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Law Division |
E16009
|
entity |
| Predicate | primaryClients |
P9839
|
FINISHED |
| Object | Members of Congress |
—
|
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: Members of Congress | Statement: [American Law Division, primaryClients, Members of Congress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryClients Context triple: [American Law Division, primaryClients, Members of Congress]
-
A.
primaryClient
chosen
Indicates that one entity serves as the main or most important client associated with another entity.
-
B.
primaryMembers
Indicates that the related entities are the main or most important members within a larger group or organization.
-
C.
primaryBeneficiaries
Indicates which entities are the main recipients or advantaged parties resulting from a particular action, resource, or arrangement.
-
D.
majorCustomer
Indicates that one entity is a primary or high-value customer of another entity, typically contributing a significant portion of business or revenue.
-
E.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66c2e108190a754c60d2eac6676 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a50348088190873a1446db657a78 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.