Triple
T17558107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMQP |
E427634
|
entity |
| Predicate | amqp10ApprovedAsOasisStandardYear |
P127931
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [AMQP, amqp10ApprovedAsOasisStandardYear, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amqp10ApprovedAsOasisStandardYear Context triple: [AMQP, amqp10ApprovedAsOasisStandardYear, 2012]
-
A.
approvedAsEcmaStandard
Indicates that something has been formally accepted and recognized as an official ECMA (Ecma International) standard.
-
B.
conventionAdoptedAt
Indicates that a convention was formally adopted or agreed upon at a specific event, meeting, or location.
-
C.
OSIApproved
Indicates that a software license has been reviewed and approved by the Open Source Initiative (OSI) as complying with its Open Source Definition.
-
D.
introducedAsInternationalStandard
Indicates that something has been formally adopted and announced as an international standard.
-
E.
firstStandardApproved
Indicates that an entity is the earliest or initial standard that has received formal approval.
- F. None of above. chosen
Provenance (4 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562413d08190acaa5272046d3626 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:50 a.m.