Triple
T1447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Institute of Electrical and Electronics Engineers |
E27
|
entity |
| Predicate | develops |
P73
|
FINISHED |
| Object | industry standards |
—
|
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 standards | Statement: [Institute of Electrical and Electronics Engineers, develops, industry standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: develops Context triple: [Institute of Electrical and Electronics Engineers, develops, industry standards]
-
A.
developed
chosen
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
-
B.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
C.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
D.
developedAt
Indicates the place or location where something was created, built, or developed.
-
E.
analyzes
Indicates that one entity systematically examines or evaluates another entity to understand its nature, structure, or components.
- 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_69a22a285828819081a58308fb963df1 |
completed | Feb. 27, 2026, 11:35 p.m. |
| NER | Named-entity recognition | batch_69a2346846608190b6b40d31f1dbd685 |
completed | Feb. 28, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69a233c396ec8190986608d07fb251d4 |
completed | Feb. 28, 2026, 12:16 a.m. |
Created at: Feb. 27, 2026, 11:36 p.m.