Triple
T23512695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Barron |
E572468
|
entity |
| Predicate | caseNameAsParty |
P15954
|
FINISHED |
| Object | Barron v. Mayor and City Council of Baltimore |
—
|
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: Barron v. Mayor and City Council of Baltimore | Statement: [John Barron, caseNameAsParty, Barron v. Mayor and City Council of Baltimore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseNameAsParty Context triple: [John Barron, caseNameAsParty, Barron v. Mayor and City Council of Baltimore]
-
A.
partyToCase
chosen
Indicates that an entity is involved in a legal case as one of its formal participants (e.g., plaintiff, defendant, or other party).
-
B.
isNamedAsPartyIn
Indicates that an entity is explicitly listed or designated as a party in a formal agreement, contract, or legal document.
-
C.
caseNameVariant
Indicates that one case name is an alternative or variant form of another case name.
-
D.
caseNameDerivedFrom
Indicates that the name of a legal case is derived from, or based on, another specified source or entity.
-
E.
namedForCourt
Indicates that one entity bears a name that was given or designated by a court or judicial authority.
- 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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa7f583881909e78e8fe2e6e25fe |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:07 p.m.