Triple
T36977914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard Occupational Classification |
E914747
|
entity |
| Predicate | firstImplemented |
—
|
GENERATED |
| Object | 1977 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstImplemented Context triple: [Standard Occupational Classification, firstImplemented, 1977]
-
A.
firstImplementedBy
Indicates that the subject was initially realized, executed, or put into practice by the specified agent or entity.
-
B.
firstPerformedWith
Indicates that an action or work was initially performed in conjunction with a specified collaborator, group, or medium.
-
C.
historicallyImplementedIn
Indicates that an action, practice, or system was carried out or put into effect in a particular place or context during a past historical period.
-
D.
fullyImplemented
Indicates that something has been completely realized, executed, or put into effect with all intended components or features in place.
-
E.
firstSupportedBy
Indicates that an entity is initially upheld, enabled, or made possible by another entity that provides its primary support.
- F. None of above. chosen
Provenance (1 batch)
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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.