Triple
T125388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Reports |
E2535
|
entity |
| Predicate | firstVolumeNumberInUSReports |
P2230
|
FINISHED |
| Object | 1 U.S. |
—
|
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: 1 U.S. | Statement: [Dallas Reports, firstVolumeNumberInUSReports, 1 U.S.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstVolumeNumberInUSReports Context triple: [Dallas Reports, firstVolumeNumberInUSReports, 1 U.S.]
-
A.
volumeInUnitedStatesReports
Indicates that a legal case or decision is published in a specified volume of the United States Reports.
-
B.
beganOfficialNumberingWith
chosen
Indicates that an entity started its formal or official numbering sequence with a specified initial number or identifier.
-
C.
firstStandardized
Indicates that an entity is the earliest or primary instance to which a standard or uniform specification has been first applied among comparable entities.
-
D.
firstEditionPrintRun
Indicates the initial quantity of copies produced when a work is printed in its first published edition.
-
E.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
- 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_69a251b54ea88190b18281669f59b4c0 |
completed | Feb. 28, 2026, 2:23 a.m. |
| NER | Named-entity recognition | batch_69a2573e4e6481908252dfef2e34f46e |
completed | Feb. 28, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69a2564a54948190ba30bee858173b27 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:27 a.m.