Triple
T35602567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Ethernet Forum |
E1028795
|
entity |
| Predicate | typeOfStandardsBody |
P203639
|
FINISHED |
| Object | industry alliance |
—
|
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: industry alliance | Statement: [Metro Ethernet Forum, typeOfStandardsBody, industry alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfStandardsBody Context triple: [Metro Ethernet Forum, typeOfStandardsBody, industry alliance]
-
A.
typeOfComplianceBody
Indicates that one entity is a compliance-related body or authority of the type specified by the other entity.
-
B.
standardsType
Indicates the classification or category of standards that apply to or are associated with an entity or activity.
-
C.
isPartOfStandardizationSystem
Indicates that something belongs to, or is included within, a defined standardization framework, scheme, or system.
-
D.
typeOfStandardizationActivity
Indicates the specific kind or category of standardization activity that is being carried out or referenced.
-
E.
hasStandardizationBody
Indicates that an entity is associated with, governed by, or defined by a specific standards-setting organization or authority.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a01bb06422c819095bb42f6f3a0e801 |
completed | May 11, 2026, 11:18 a.m. |
| PD | Predicate disambiguation | batch_6a01b9991c348190ac49b65ea2fd86ed |
completed | May 11, 2026, 11:12 a.m. |
| PDg | Predicate description generation | batch_6a01bb0584608190a27ad07f095ea7fd |
completed | May 11, 2026, 11:18 a.m. |
Created at: May 3, 2026, 4:05 p.m.