Triple
T36583991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 21 How. 506 |
E902472
|
entity |
| Predicate | reporterFullName |
P186522
|
FINISHED |
| Object | Howard’s Supreme Court Reports |
—
|
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: Howard’s Supreme Court Reports | Statement: [21 How. 506, reporterFullName, Howard’s Supreme Court Reports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reporterFullName Context triple: [21 How. 506, reporterFullName, Howard’s Supreme Court Reports]
-
A.
creatorFullName
Indicates the full personal name of the entity that created or authored another entity.
-
B.
reporter
Indicates that an entity acts in the role of a reporter, typically gathering, writing, or presenting information or news about another entity or event.
-
C.
reporterType
Indicates the specific role or category of reporter associated with an entity or event.
-
D.
fullNameInCredits
Indicates that an entity’s complete name is listed in the official credits of a work.
-
E.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:11 p.m.