Triple
T2188067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFC |
E49795
|
entity |
| Predicate | introducedAsStandard |
P5655
|
FINISHED |
| Object | early 2000s |
—
|
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 2000s | Statement: [NFC, introducedAsStandard, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsStandard Context triple: [NFC, introducedAsStandard, early 2000s]
-
A.
introducedInStandard
chosen
Indicates that something (such as a concept, feature, or element) was first defined or formally specified in a particular standard.
-
B.
becameStandardFor
Indicates that something was adopted and established as the usual or accepted norm for a particular purpose, context, or group.
-
C.
firstStandardApproved
Indicates that an entity is the earliest or initial standard that has received formal approval.
-
D.
firstStandardized
Indicates that an entity is the earliest or primary instance to which a standard or uniform specification has been first applied among comparable entities.
-
E.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.