Triple
T13106908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USAR19000084 |
E310865
|
entity |
| Predicate | uniqueIdentifierWithinYear |
P12446
|
FINISHED |
| Object | 000084 |
—
|
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: 000084 | Statement: [USAR19000084, uniqueIdentifierWithinYear, 000084]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniqueIdentifierWithinYear Context triple: [USAR19000084, uniqueIdentifierWithinYear, 000084]
-
A.
yearType
Indicates the classification or category assigned to a specific year (e.g., academic, fiscal, calendar, leap).
-
B.
hasNumberInYear
chosen
Indicates that a specific number is associated with or occurs within a given year.
-
C.
sharesYearNumberingWith
Indicates that two calendar systems or date representations use the same numbering for years, so a given year has the same numeric label in both.
-
D.
authorizationYear
Indicates the year in which an official approval, permission, or authorization for something was granted.
-
E.
hasLetterNumberInYear
Indicates that a specific letter or document is assigned a particular sequential number within a given year.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98154c9f48190aeca779d97151759 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:05 p.m.