Triple
T312744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Library of Congress Subject Headings |
E7641
|
entity |
| Predicate | startUseYear |
P10338
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Library of Congress Subject Headings, startUseYear, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startUseYear Context triple: [Library of Congress Subject Headings, startUseYear, early 20th century]
-
A.
settingStartYear
Indicates the year in which a particular setting, configuration, or condition first becomes effective or begins to apply.
-
B.
beganInYear
chosen
Indicates that an event, process, or state started in a specific calendar year.
-
C.
firstPlanStartYear
Indicates the calendar year in which an entity’s initial plan or planning period begins.
-
D.
transitionYear
Indicates the specific year in which a change, shift, or transition from one state, condition, or phase to another occurs.
-
E.
isUsedAllYear
Indicates that something is utilized or remains in active use throughout the entire year, without being limited to a particular season or period.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4aa16881909b2c8404b85992df |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e9428098819089d5950cd2c96dc4 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.