Triple
T9030469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEC technical committee |
E216153
|
entity |
| Predicate | hasOutputUser |
P85779
|
FINISHED |
| Object | manufacturers |
—
|
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: manufacturers | Statement: [IEC technical committee, hasOutputUser, manufacturers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutputUser Context triple: [IEC technical committee, hasOutputUser, manufacturers]
-
A.
hasOutputStatus
Indicates that an entity is associated with a particular state or condition of its produced output.
-
B.
hasUser
Indicates that an entity is associated with or linked to a specific user.
-
C.
hasOutputType
Indicates that an entity produces, returns, or yields a result of a specified type.
-
D.
hasOutputStructure
Indicates that an entity produces, defines, or is associated with a particular structural form or arrangement as its output.
-
E.
hasUserService
Indicates that an entity is associated with or utilizes a particular user-related service.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9e0aa881908886f453c51ecd0e |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:08 p.m.