Triple
T31317160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USBMR1400128 |
E798626
|
entity |
| Predicate | componentYearOfReference |
P68415
|
FINISHED |
| Object | 14 |
—
|
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: 14 | Statement: [USBMR1400128, componentYearOfReference, 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentYearOfReference Context triple: [USBMR1400128, componentYearOfReference, 14]
-
A.
yearOfReference
chosen
Indicates the specific year to which a statement, measurement, or data point is intended to apply or be interpreted with reference.
-
B.
accessionYear
Indicates the calendar year in which an item, record, or entity was formally added to or registered within a collection, system, or institution.
-
C.
yearOfProduction
Indicates the specific year in which an item, work, or product was created or manufactured.
-
D.
definitionYear
Indicates the year in which something was formally defined, established, or given its official definition.
-
E.
yearOfIdentification
Indicates the specific year in which an entity was first identified, discovered, or formally recognized.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 29, 2026, 9:15 p.m.