Triple
T32896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Reports |
E656
|
entity |
| Predicate | beganOfficialNumberingWith |
P2230
|
FINISHED |
| Object | volume 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: volume 1 U.S. | Statement: [United States Reports, beganOfficialNumberingWith, volume 1 U.S.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganOfficialNumberingWith Context triple: [United States Reports, beganOfficialNumberingWith, volume 1 U.S.]
-
A.
wasFirstBuiltInYear
Indicates that the initial construction of an entity was completed in a specified year.
-
B.
firstCelebratedInYear
Indicates the year in which something (such as an event, holiday, or celebration) was first observed or celebrated.
-
C.
firstAwarded
Indicates the time or occasion when an award, honor, or recognition was given for the very first time.
-
D.
retiredNumber
Indicates that an entity (typically a team or organization) has formally withdrawn a specific number from future use, usually to honor a particular individual or achievement associated with that number.
-
E.
yearSigned
Indicates the specific year in which an agreement, contract, or document was formally signed.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2496ffc548190b545f998cbebd5b9 |
completed | Feb. 28, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69a248717f5081909952a8c9ed1e1742 |
completed | Feb. 28, 2026, 1:44 a.m. |
| PDg | Predicate description generation | batch_69a2496f21708190a0fd33e269b9917f |
completed | Feb. 28, 2026, 1:48 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.