Triple
T38490424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montgomery City Lines |
E918038
|
entity |
| Predicate | subjectToCourtRuling |
P11395
|
FINISHED |
| Object | Browder v. Gayle (1956) |
—
|
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: Browder v. Gayle (1956) | Statement: [Montgomery City Lines, subjectToCourtRuling, Browder v. Gayle (1956)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToCourtRuling Context triple: [Montgomery City Lines, subjectToCourtRuling, Browder v. Gayle (1956)]
-
A.
overseenByCourt
Indicates that an action, process, or entity is subject to supervision, authority, or control by a court.
-
B.
courtOrdered
chosen
Indicates that an action, condition, or relationship exists because it has been formally mandated or imposed by a court order.
-
C.
heldCourtUnder
Indicates that one authority conducted judicial or ceremonial court proceedings under the jurisdiction, auspices, or authority of another.
-
D.
heldCourtIn
Indicates that an authority or governing body formally conducted judicial or official proceedings in a particular place.
-
E.
heldByCourt
Indicates that a particular legal position, opinion, or decision is asserted or determined by a court.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 3, 2026, 4:31 p.m.