Triple
T6033429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayer Brown |
E134360
|
entity |
| Predicate | hasMultipleJurisdictions |
P11977
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mayer Brown, hasMultipleJurisdictions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleJurisdictions Context triple: [Mayer Brown, hasMultipleJurisdictions, true]
-
A.
hasMemberJurisdictions
Indicates that an administrative or organizational entity includes specific jurisdictions as its constituent members.
-
B.
numberOfJurisdictions
Indicates the count of distinct legal or administrative jurisdictions associated with or applicable to an entity or situation.
-
C.
jurisdictionSharedBy
chosen
Indicates that legal or administrative authority over a matter, area, or entity is jointly held by multiple jurisdictions or governing bodies.
-
D.
consolidatedJurisdictionOf
Indicates that legal authority or control over multiple areas or cases has been combined and is exercised under a single jurisdiction.
-
E.
hasJurisdictionOver
Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
- 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b220608190b156be95632cf3b3 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.