Triple
T31346997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judge Harry Pregerson Interchange |
E799472
|
entity |
| Predicate | officialNameHonors |
P116229
|
FINISHED |
| Object | Judge Harry Pregerson |
—
|
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: Judge Harry Pregerson | Statement: [Judge Harry Pregerson Interchange, officialNameHonors, Judge Harry Pregerson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialNameHonors Context triple: [Judge Harry Pregerson Interchange, officialNameHonors, Judge Harry Pregerson]
-
A.
nameHonors
Indicates that a name is given to honor, commemorate, or pay tribute to a particular entity.
-
B.
namedInHonorBy
chosen
Indicates that one entity has been used as the namesake or dedicatee by another entity, signifying that the latter is named in honor of the former.
-
C.
alsoHonoredAs
Indicates that an entity is additionally recognized or celebrated under another title, role, or form of honor beyond its primary designation.
-
D.
officialNameGivenBy
Indicates that an official or formal name has been assigned to an entity by a specific authority or source.
-
E.
officialName
Indicates the formally recognized name assigned to an entity by an authoritative body or source.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: April 29, 2026, 9:17 p.m.