Triple
T35513856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humberto Munoz-Flores |
E1026357
|
entity |
| Predicate | caseHeWasIn_citation |
P183791
|
FINISHED |
| Object | 495 U.S. 385 |
—
|
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: 495 U.S. 385 | Statement: [Humberto Munoz-Flores, caseHeWasIn_citation, 495 U.S. 385]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseHeWasIn_citation Context triple: [Humberto Munoz-Flores, caseHeWasIn_citation, 495 U.S. 385]
-
A.
caseHeBrought
Indicates that a male subject initiated and brought a legal case or lawsuit against another party.
-
B.
usedInLegalCitation
Indicates that one entity is referenced or relied upon as an authoritative source within a legal citation to support legal arguments or decisions.
-
C.
usedInCourts
Indicates that something is employed or applied within legal court settings, such as in judicial proceedings or courtroom processes.
-
D.
legalCitation
Indicates that one legal document, case, or authority formally references or cites another as a source of legal support or precedent.
-
E.
appearsInCourt
Indicates that an entity is formally present and participating in a legal proceeding before a court.
- F. None of above. chosen
Provenance (4 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: May 3, 2026, 4:04 p.m.