Triple
T463789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3bz 2.5G/5GBASE‑T Ethernet standard |
E7399
|
entity |
| Predicate | approvalDate |
P14303
|
FINISHED |
| Object | September 2016 |
—
|
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: September 2016 | Statement: [IEEE 802.3bz 2.5G/5GBASE‑T Ethernet standard, approvalDate, September 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approvalDate Context triple: [IEEE 802.3bz 2.5G/5GBASE‑T Ethernet standard, approvalDate, September 2016]
-
A.
proposalDate
Indicates the date on which a proposal is formally made or submitted from one entity to another.
-
B.
acknowledgmentDate
Indicates the date on which an acknowledgment of something (such as receipt, notice, or information) is formally recorded or recognized.
-
C.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
D.
announcementDate
Indicates the date on which an announcement is formally made or becomes publicly known.
-
E.
decisionDate
Indicates the date on which a specific decision was formally made or finalized.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efc214788190a8dff20fec4412e0 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2ede8eac081908dffade6a5e7950b |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef06d2fc8190b379d575215a8518 |
completed | Feb. 28, 2026, 1:35 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.