Triple
T28769578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muller v. Oregon |
E726372
|
entity |
| Predicate | briefPreparedBy |
P48513
|
FINISHED |
| Object | Louis D. Brandeis |
—
|
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: Louis D. Brandeis | Statement: [Muller v. Oregon, briefPreparedBy, Louis D. Brandeis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: briefPreparedBy Context triple: [Muller v. Oregon, briefPreparedBy, Louis D. Brandeis]
-
A.
preparationBy
chosen
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
B.
preparedUnder
Indicates that something was created, processed, or made while being subject to the authority, supervision, or conditions established by a particular person, organization, or standard.
-
C.
preparedAt
Indicates the time or place at which something was prepared or made ready.
-
D.
preparationSupervisedBy
Indicates that the preparation of something is carried out under the oversight or direction of a supervising entity.
-
E.
preparedWithin
Indicates that an item or outcome is created, completed, or made ready within a specified time frame or duration.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:15 a.m.