Triple
T21916913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATS-SN |
E541202
|
entity |
| Predicate | implementedSince |
P26568
|
FINISHED |
| Object | late 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: late 20th century | Statement: [ATS-SN, implementedSince, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedSince Context triple: [ATS-SN, implementedSince, late 20th century]
-
A.
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.
-
B.
implementedOn
Indicates that something (such as a feature, standard, or specification) is realized, executed, or put into effect within or on a particular platform, system, or environment.
-
C.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
-
D.
appliedSince
chosen
Indicates that a particular condition, rule, status, or action has been in effect starting from a specified point in time and continues from that date onward.
-
E.
supportsSinceVersion
Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1233858308190a877d8015db4d380 |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:43 p.m.